ID: Q89131
5.00 5.10 1.00 1.00a | 5.00 5.10 | 1.00 4.00
MS-DOS | OS/2 | WINDOWS NT
kbprb
The information in this article applies to:
LEN_TRIM may appear to return an incorrect trimmed string length. This occurs when the string in the calling routine is not initialized and the subprogram's formal argument declares the character string smaller than the original string's length.
All bytes in uninitialized strings are set to zero (null characters). When a string is initialized, any unused bytes are padded with spaces to the end of the string. The padding is done to the size that is declared in the routine in which the string is initialized. If a string is passed to a routine that declares the string size to be smaller then it was defined, the string will be incompletely padded with spaces. Upon return to the routine where the string was declared, the string will still have null characters at the end. The LEN_TRIM intrinsic function only parses for spaces and will stop immediately when it detects the final null character. This will appear to be incorrect because most editors display null characters as blanks.
LEN_TRIM works correctly if the string lengths are declared equal in all routines that the use the string. Also, initializing the string to all spaces in the routine in which it is originally declared will also correct the problem.
character work*80
integer len
call getstr(work)
len = LEN_TRIM(work)
print *,len ! len will be 80
end
subroutine getstr(outstr)
character outstr*45
outstr = 'This is a test'
return
end
character work*80
integer len
work = ' '
call getstr(work)
len = LEN_TRIM(work)
print *,len ! len will be 14
end
subroutine getstr(outstr)
character outstr*45
outstr = 'This is a test'
return
end
Additional reference words: 4.00 5.00 5.10 1.00
KBCategory: kbprb
KBSubcategory: FORTLngIss
Keywords : kbcode kbFortranPS kbLangFortran
Version : 5.00 5.10 1.00 1.00a | 5.00 5.10
Platform : MS-DOS NT OS/2 WINDOWS
Last Reviewed: May 23, 1998