Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!usc!apple!sun-barr!newstop!texsun!digi.lonestar.org!woodwrk!dick From: dick@woodwrk.UUCP (Richard H. Wood) Newsgroups: comp.sys.amiga.tech Subject: Re: manx aztec c 5.0a bugs? Message-ID: Date: 11 Aug 90 16:31:58 GMT References: Lines: 46 >In article josef@augs.ccs.imp.com (Josef Egloff) writes: >...in the includefile functions.h...there are some >bugs (I think). the functions Examine() and ExNext are not correct. > >the include file reads > >long Examine (BPTR lock, BPTR FileInfoBlock); >and >long ExNext (BPTR lock, BPTR FileInfoBlock); > >... I think the prototypes should be like this > >long Examine (BPTR lock, struct FileInfoBlock *fib); >and >long ExNext (BPTR lock, struct FileInfoBlock *fib); > >is this correct? ...are there more such bugs in aztec 5.0a? Yes, that's correct. And yes, there are other bugs in 5.0a includes. Here's what they actually look like in Aztec 5.0b, functions.h: long Examine(BPTR lock, struct FileInfoBlock *fileInfoBlock); and long ExNext(BPTR lock, struct FileInfoBlock *fileInfoBlock); Try to upgrade to Aztec 5.0c. I understand it's the same as 5.0b...they just changed the installation program in 5.0c, as I understand it. I rebuilt MG3a with 5.0c includes and had NONE of the warnings which the (MG) documentation indicated were benign, but none-the-less a result of bad prototypes in 5.0a. However, I've had to fall back to the 5.0a COMPILER to get MG3a to actually run. Anybody else run into this? >cu josef > >-- >< Josef Egloff | USENET: josef@augs.ccs.imp.com > >< Pfaffnernweg 19 | PATH: impch!accsys!augs!josef > >< CH - 4852 Rothrist | CBMNET: cbmswi!augs1!jegloff > >< Switzerland | AUGS: as SYSOP (acc #1) > -- | | uunet!digi!woodwrk!dick Dick Wood | Become an ORGAN DONOR : dwood@digi.lonestar.org --