home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ncar!noao!amethyst!organpipe.uug.arizona.edu!news
- From: dave@cs.arizona.edu (Dave Schaumann)
- Newsgroups: comp.lang.c
- Subject: Re: Help! what's wrong with this program?
- Message-ID: <1992Sep7.003543.1055@organpipe.uug.arizona.edu>
- Date: 7 Sep 92 00:35:43 GMT
- References: <1992Sep6.041410.16388@eng.ufl.edu> <1992Sep6.152442.25878@en <1992Sep6.203612.17566@mnemosyne.cs.du.edu>
- Sender: news@organpipe.uug.arizona.edu
- Reply-To: dave@cs.arizona.edu (Dave Schaumann)
- Distribution: usa
- Organization: University of Arizona
- Lines: 19
- In-Reply-To: swalter@nyx.cs.du.edu (DreamWeaver)
-
- In article <1992Sep6.203612.17566@mnemosyne.cs.du.edu>, swalter@nyx (DreamWeaver) writes:
- >
- >Correct me if I'm wrong (lord knows that will happen ;) ... but doesn't
- >the line
- >
- > *bp++ = c;
- >
- >in the pusch() function actually mean (as far as order of precedence):
- >
- > (*bp)++ = c;
-
- No. "*bp++" is definitely a popular idiom among C pointer-hackers...
-
- >Call me kooky ...
-
- By your command, kooky.
-
- --
- Dave Schaumann dave@cs.arizona.edu
-