Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ncar!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.programmer Subject: Re: Aztec C 5.0d w/ 2.0 includes. Char vs. UBYTE Message-ID: <19222@cbmvax.commodore.com> Date: 22 Feb 91 06:20:06 GMT References: <19176@cbmvax.commodore.com> <2169@fornax.UUCP> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Distribution: na Organization: Commodore, West Chester, PA Lines: 19 In article <2169@fornax.UUCP> laughlin@lccr.UUCP (Bob Laughlin) writes: >In article <19176@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes: >> Always has been BPTR, anyone who uses FileLock * is setting >>themselves up for a nasty suprise. > > Then why do the Autodocs have things like, >struct FileLock *DupLock (struct FileLock *lock) ; >when they document dos functions? I thought Manx was just being lazy >in calling all dos pointers BPTR's. Because the people who wrote it were used to programming in BCPL. It's been fixed. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)