From: "Lawrence Rust" Newsgroups: comp.os.msdos.djgpp References: <200301280550 DOT h0S5ohlA017021 AT chac DOT its DOT uow DOT edu DOT au> <3E368CAE DOT 3F4AD13 AT phekda DOT freeserve DOT co DOT uk> Subject: Re: scan() in c++ Lines: 18 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: Date: Tue, 28 Jan 2003 15:12:27 -0000 NNTP-Posting-Host: 62.253.142.146 X-Complaints-To: abuse AT ntlworld DOT com X-Trace: newsfep4-win.server.ntli.net 1043766754 62.253.142.146 (Tue, 28 Jan 2003 15:12:34 GMT) NNTP-Posting-Date: Tue, 28 Jan 2003 15:12:34 GMT Organization: ntl Cablemodem News Service To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Richard Dawe" wrote... [snip] > There are right and wrong ways of including stdio in C++ programs. The wrong > way is . The right way is . This is what Hans-Bernhard means, > I think. Using #include in an ANSI c++ program is still perfectly legal (see ISO 14882 Annex D.5). It includes the cname form header and then brings each name into scope with a using declaration. The right way (IMHO) is not to use c++ stream i/o. -- Lawrence Rust