From: "bowman" <bowman AT montana DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990418140925 DOT 22615c-100000 AT is> <sMlS2.2355$R93 DOT 22629 AT newsfeed DOT slurp DOT net> <37252A95 DOT 5894 AT arcticmail DOT com> <eH9V2.1527$n5 DOT 4471 AT newsfeed DOT slurp DOT net> <37260199 DOT 6FFD6B6D AT pacificnet DOT net>
Subject: Re: Challenge for C++ programmers:
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Message-ID: <9VrV2.132$Sx.1785@newsfeed.slurp.net>
Date: Tue, 27 Apr 1999 17:39:05 -0600
NNTP-Posting-Host: 208.26.212.131
X-Trace: newsfeed.slurp.net 925256389 208.26.212.131 (Tue, 27 Apr 1999 18:39:49 CDT)
NNTP-Posting-Date: Tue, 27 Apr 1999 18:39:49 CDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Ralph Gesler <rgesler AT pacificnet DOT net> wrote in message
news:37260199 DOT 6FFD6B6D AT pacificnet DOT net...
>
> All errata for Stroustrup's 3rd edition, up through the 9th printing are
> available at http://www.research.att.com/~bs/3rd_errata.html.

thanks  for that link. Now, if I could get sed to work on hardcopy books
.....

>         "Note that on some systems, it can be hard to determine if input
> is available.
>         Thus, in_avail() might be (poorly) implemented to return 0
>         in cases where an input operation would succeed."

I didn't spend too much time playing with it, and I must confess I can't
recall which compiler I was using (CygWin or DJGPP g++, or Ming's egcs), but
the behavior I saw was consistent with in_avail() always returning 0. I
guess a little more controlled test is in order.