BUG: GetStrQQ Leaves Characters in Standard OutputLast reviewed: March 15, 1996Article ID: Q106529 |
The information in this article applies to:
SYMPTOMSThe intrinsic function GetStrQQ leaves spurious characters in the standard output buffer that are displayed on the next statement that flushes the buffer.
RESOLUTIONUse the READ statement instead of GetStrQQ for reading from the standard input device. Alternatively, the GetCharQQ function may be used within a DO loop.
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONContrary to the documentation, there is no advantage to using GetStrQQ rather than READ for standard I/O. Run the sample code below, and enter any string when prompted. The output has a blank line under "Enter string: abc" but not under "Enter another string: abc", and in addition there is an extra space in front of the first 1000. GetStrQQ produces the extra linefeed and space characters, whereas the standard READ statement does not.
Output
Enter string: abc 1000 2000 Enter another string: abc 1000 2000 Sample CodeC No compiler options required
include 'flib.fi' include 'flib.fd' character string*10 write(*,'('' Enter string: ''\)') len = getstrqq(string) do i = 1,2 write(*,*) i*1000 end do write(*,'('' Enter another string: ''\)') read(*,'(a)') string do i = 1,2 write(*,*) i*1000 end do end |
Additional reference words: 1.00 1.00a 4.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |