Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!apple!agate!stanford.edu!eos!aio!gwharvey From: gwharvey@lescsse.jsc.nasa.gov (Greg Harvey) Newsgroups: comp.sys.amiga Subject: Re: lattice C NOVICE question Message-ID: Date: 31 Mar 91 22:01:10 GMT References: <588.27ED7F66@casino.FIDONET.ORG> Sender: news@aio.jsc.nasa.gov (USENET News System) Organization: Lockheed Engineering and Sciences Lines: 37 In <588.27ED7F66@casino.FIDONET.ORG> Petri.Pusa@p2.f501.n220.z2.FIDONET.ORG (Petri Pusa) writes: > > >#include "libraries/dosextens.h" > > > > This should be: > > > > #include > >What's the big difference ? I doubt that anybody has a libraries >directory including dosextens.h by a mistake in that directory where >(s)he is compiling from so that the information would get mixed up. > > > >extern struct FileHandle *Open(); > > > > > That will work, but technically, it should be: > > > > extern BPTR Open(); >How about #include ? And again that doesn't have any >effect to the program code. Perhaps it's technically right, but why not >use the header files made by Commodore which should be technically >always right ? I know this has been discussed before, so I'm following up with a reminder. SAS/Lattice C's lclib redefines several Amiga DOS library routines. If you use lclib, you "preempt" the Amiga DOS library routines. This means you SHOULD use lattice includes when doing ANSI-compatible programming. Another reason is that SAS/Lattice handles library calls in a specific, optimized, NON-ANSI fashion if the SAS/Lattice prototypes are used and the proper compile options are used. -- If you get the impression I'm not qualified to speak for my company, it's because I ain't, I can't, I don't, I won't, and I don'wanna. Greg Harvey --Temporarily without mail service Lockheed, Houston Texas --Hope to have a PSCNI route soon!