Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!YALE.ARPA!LEICHTER-JERRY
From: LEICHTER-JERRY@YALE.ARPA
Newsgroups: mod.computers.vax
Subject: Re: Potential C problem
Message-ID: <8607080947.AA11148@ucbvax.Berkeley.EDU>
Date: Tue, 8-Jul-86 05:47:31 EDT
Article-I.D.: ucbvax.8607080947.AA11148
Posted: Tue Jul  8 05:47:31 1986
Date-Received: Tue, 8-Jul-86 19:04:25 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: <LEICHTER-JERRY@YALE.ARPA>
Organization: The ARPA Internet
Lines: 25
Approved: info-vax@sri-kl.arpa


    > Known bug; I believe it's fixed in VAX C V2.2.

    The bug involving sscanf's not recognizing a 0 as a hex digit is still in
    VAX-C V2.2-015.  It is the result of scanf's strategy for dealing with
    integer conversions, in which it "optimizes" by skipping leading zero's.
    To merely state that it's a "known bug" is of little help to somebody
    trying to work around it.  You need either to list all cases in which the
    bug occurs or give a description of what the problem REALLY is.

All I knew about the bug was what I said:  That it had been reported before.
I didn't know the origin, nor did I have any direct way to check that it WAS
fixed in 2.2, only that it WASN'T fixed in 2.1, the latest version installed
here.  Because of the timing of the reports, I'm surprised that it wasn't
fixed in VAX C V2.2.  On the other hand, this is a problem in VAXCRTL, which
is no longer shipped with the VAX C kit, but directly with VMS.  So the right
answer might be "fixed in VMS V4.4" (which we don't have installed yet
either....))

You are certainly welcome to provide more information if you have it.  I
posted my message to (perhaps) save people unnecessary time staring at their
programs and the documentation, trying to figure out what THEY had done wrong.

							-- Jerry
-------