Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: Re: Potential C problem
Message-ID: <860704091050.004@CitHex.Caltech.Edu>
Date: Fri, 4-Jul-86 12:10:59 EDT
Article-I.D.: CitHex.860704091050.004
Posted: Fri Jul  4 12:10:59 1986
Date-Received: Sat, 5-Jul-86 12:46:38 EDT
References: <8607010910.AA06212@csvax.caltech.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 7
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.