X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: Manni Heumann Newsgroups: comp.os.msdos.djgpp Subject: Re: File bad() problem - bug in djgpp or is it me??? Date: 19 Jan 2002 16:18:16 GMT Lines: 20 Message-ID: References: <3c47248f DOT 7781706 AT news DOT ntlworld DOT com> <3c474cca DOT 18082698 AT news DOT ntlworld DOT com> <3c4891c6 DOT 3850646 AT news DOT ntlworld DOT com> NNTP-Posting-Host: ppp164-167.uni-bielefeld.de (129.70.164.167) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: fu-berlin.de 1011457096 33658910 129.70.164.167 (16 1428 [54749]) User-Agent: Xnews/L5 X-Face: "c)Go+A65AgR*9'!B)BMLM$kYg6HDG!_g'DAsj*ALo%=kp{X&abs&t\G0F~*r?VRj#|4=6)M.RJPnD]Ql:B<-7A^EAYFpDpZRMoJy?80^3B3b AT DXb%MTyOD.*4wu&Xt6o*+6`r5E To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Kevin Dickerson wrote: > On 18 Jan 2002 02:53:35 GMT, "A. Sinan Unur" > wrote: > [...] >>does it work is you replace bad() with is_open()? > > Tried that, and it still isn't playing ball, might try and > d/l an earlier version of gcc and see if that works, then > if it does put a fault in. Could this be a problem with the standard, i.e. our understanding of the standard? We have good(), fail(), and bad(). And bad() is only supposed to return true, when characters have been lost while reading from a file. What do good() and fail() say in your case? I never test bad() in such cases, because fail() will complain much earlier. Manni