Newsgroups: comp.sys.novell Path: utzoo!utdoe!contact!yung From: yung@contact.uucp Subject: Re: Watcom C & Novell. Reply-To: yung@contact.UUCP () Organization: Contact Public Unix BBS. Toronto, Canada. Date: Thu, 28 Mar 91 19:32:54 GMT Message-ID: <1991Mar28.193254.24432@contact.uucp> References: <1991Mar22.105548.3212@waikato.ac.nz> <708@svcs1.UUCP> Jim Serwer writes: >In article <1991Mar22.105548.3212@waikato.ac.nz> hamish@waikato.ac.nz writes: >> >>After all the problems I have been having with the code generated by TurboC, I >>have decided to change compilers for my Novell developement work. So, does >>anyone on the net have experience with the Novell C compiler? >>-- >>============================================================================== >>| Hamish Marson | > > (stuff deleted) > >Sorry I have never used Watcom. But I do have a question and a comment >on TurboC. > >Question: What version of TurboC are you using? What is the nature >of your problems? > >Comment: I am using Borland C++ v2.0 and NetWare C Interface for DOS (CID) >v1.10. I have reported a number of bugs to Borland for the Development >Environment, but never for the compiler. In fact, I have one program >that bombs when compiled by MSC 5.1 and works when compiled by Borland C++. > >Jim Serwer I started out using the Watcom C compiler to write VAPs. But I decided to give it up after getting really frustrated with the documentations. Now I am using Turbo C++ 2.0. At this moment, I am still feeling my way with the new compiler and keeping my finger crossed that it will work with netware. Anybody got comment on how well Turbo C++ will work on netware? As I see it, I would MUCH rather use assembly, except Novell charge $200 for their system call libaries. Am I the only one that think this kind of robbery should be outlawed? -Amos Yung -- ******************************************************************************* Amos Yung * " Don't be silly. Of course the plane email: * won't crash. *I* am on it!!! " utai!contact * -Murphy Brown.