delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
Message-ID: | <1ea101c4918e$6aa2e360$0600000a@broadpark.no> |
From: | "Gisle Vanem" <giva AT bgnett DOT no> |
To: | "djgpp" <djgpp AT delorie DOT com> |
References: | <20040902144152 DOT GH6858 AT webhome DOT cz> <41376655 DOT 2A1807EC AT yahoo DOT com> <a4tej0ha3ogninujdhurgel3jcn0r441m2 AT 4ax DOT com> <200409022030 DOT i82KUYUY004665 AT envy DOT delorie DOT com> <41378AAC DOT 9060805 AT acm DOT org> <200409022141 DOT i82Lf3d9005713 AT envy DOT delorie DOT com> |
Subject: | Re: scanf: strange behavior? |
Date: | Fri, 3 Sep 2004 10:17:13 +0200 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook Express 6.00.2800.1437 |
X-MimeOLE: | Produced By Microsoft MimeOLE V6.00.2800.1441 |
Reply-To: | djgpp AT delorie DOT com |
> > Can I surmise the implementation choice at DJGPP was the '"correct"'? > > I don't recall offhand if the current (or past) implementation in > DJGPP was fully correct or not, but if it's different from glibc or > borland, it's certainly not the "compatible" option ;-) Hasn't anybody mentioned that sscanf() in djgpp 2.04 has a bug? Don't know who reported it first, but I did here: http://www.delorie.com/archives/browse.cgi?p=djgpp-workers/2004/03/27/06:45:38 So the OP uses 2.04 and sees the result of this bug? (since 2.03 produces the expected result). It seems the bug has been fixed now (by Martin S.?) This http://www.ludd.luth.se/~ams/djgpp/cvs/djgpp/src/libc/ansi/stdio/doscan.c hash a timestamp of 3 Sep 2004. Good work. --gv
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |