Greetings!
"Mike Thomas" <[EMAIL PROTECTED]> writes:
> > Have you any idea why this new error might have recently
> > crept into the Windows build of both HEAD and 268pre?
>
> Found it - the following new lines in read.d:
>
> while (listen_stream(in)) {
> object c=read_char(in);
> if (cat(c)!=cat_whitespace) {
> unread_char(c,in);
> break;
> }
> }
>
> One of the places where listen_stream is used in read.d is #ifdefed out
> on the macro LISTEN_FOR_INPUT (defined for Linux but not Windows).
>
> I wonder whether this might be appropriate in the above case?
>
I see I misread your question earlier -- LISTEN_FOR_INPUT is only to
tell if a subsequent read will not block, i.e. there is some char on
the stream, including eof. What we do above is swallow trailing
top-level whitespace.
Take care,
> Cheers
>
> Mike Thomas.
>
>
>
>
--
Camm Maguire [EMAIL PROTECTED]
==========================================================================
"The earth is but one country, and mankind its citizens." -- Baha'u'llah
_______________________________________________
Gcl-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gcl-devel
