Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!rutgers!elbereth.rutgers.edu!bartz From: bartz@elbereth.rutgers.edu (Edward Bartz) Newsgroups: comp.sys.amiga.programmer Subject: Aztec C 5.0d w/ 2.0 includes. Char vs. UBYTE Message-ID: Date: 20 Feb 91 15:22:46 GMT Distribution: na Organization: Rutgers Univ., New Brunswick, N.J. Lines: 22 I have noticed something rather strange, in changing over from 5.0a with 1.3 includes to 5.0d with 2.0 includes. Many system routines that formerly expected (Char *) parameters now expect (UBYTE *) parameters. While this is a small difference requireing type casting, it is a pain to change all my source code. Is this a perminent change (either bye manx or commodore), or is this just a temporary screw up by Manx, to be corrected in the next update? On a similar note, I notice that source code written by other people (that use FileLocks) declare variables of the form struct FileLock * fl;. And then, pass then to Lock,Unlock,etc. In Manx, these routines have always been BPTR's. While I understand, that these routines expect BPTR's, it seem that other compiliers (SAS I assume) either declare file lock ptr's as BPTR's or automatically convert during compiling. What's the story? Ed Bartz -- UUCP: bartz@elbereth.uucp BITNET: bartz@rutphy.bitnet USSnail: 12 Roosevelt St. South River, NJ 08882