home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!swrinde!gatech!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!iies.ecn.purdue.edu!psmith
- From: psmith@iies.ecn.purdue.edu (Paul Smith)
- Newsgroups: comp.lang.c++
- Subject: Re: Bizarre Borland stream bug
- Message-ID: <1992Jul30.193832.2535@noose.ecn.purdue.edu>
- Date: 30 Jul 92 19:38:32 GMT
- References: <1992Jul30.185327.662@news2.cis.umn.edu>
- Sender: news@noose.ecn.purdue.edu (USENET news)
- Organization: Purdue University Engineering Computer Network
- Lines: 33
-
- In article <1992Jul30.185327.662@news2.cis.umn.edu> wright@epx.cis.umn.edu (Mark Wright) writes:
- >
- >/*
- >FILE 1:
- >0001 111111.1111 111111.1111
- >0009 222222.2222 222222.2222
- >
- >PROGRAM OUTPUT:
- >1: 111111.1111, 111111.1111
- >0: 9, 222222.2222
- >
- >
- >FILE 2:
- >0009 222222.2222 222222.2222
- >0001 111111.1111 111111.1111
- >
- >PROGRAM OUTPUT:
- >0: 9, 222222.2222
- >25614: 0.2222, 1
- >-19961: 0.1111, 111111.1111
- >*/
-
- Looks kinda like it is reading 0009 as an octal constant because of
- the leading zeros, except that 9 isn't a valid octal digit so it gets
- bumped to the next read.
-
- Is this correct behavior? I dunno.
-
- -Paul
- //
- // Paul F. Smith - ADPC - Purdue University
- // psmith@ecn.purdue.edu or pfsmith@adpc.purdue.edu
- //
-