Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!comp.vuw.ac.nz!cavebbs!frank From: frank@cavebbs.gen.nz (Frank van der Hulst) Newsgroups: comp.os.msdos.programmer Subject: Re: TurboC and TurboC++ Message-ID: <1991Jan09.194126.14780@cavebbs.gen.nz> Date: 9 Jan 91 19:41:26 GMT References: <350bahrd@yoda.byu.edu> <1991Jan8.195900.28885@murdoch.acc.Virginia.EDU> Distribution: comp Organization: The Cave MegaBBS, Public Access Usenet, Wellington, NZ Lines: 18 In article <1991Jan8.195900.28885@murdoch.acc.Virginia.EDU> Ran Atkinson writes: B > >ALL of the C code I had working cleanly under TC 2.0 compiled as is without >any code changes for TC++ 1.00. There was no "porting" effort at all. >Apparently Borland is trying to be safe in what they claim. The only new warning that came up for me related to pointers to functions, specifically using qsort(). On another note, upgrading to either TC++ or TP 6.0 should not be contemplated if you're using a machine less than about a 12MHz 286 with a fast HD. The VROOM system used does a lot of swapping to/from a HD. -- Take a walk on the wild side, and I don't mean the Milford Track.