mnjafar@wsuiar.wsu.ukans.edu (06/18/91)
My company is considering buying a C++ compiler, we are runing SCO/V3.2. So far we have only contacted SCO and Zortech. Do any other vendors support C++ for the SCO platform ? Has any of you guys out there used either one of the above compilers, and what do you think of them ? Any help will be appreciated. Mohammad Jafar mnjafar@wsuiar.wsu.ukans.edu jafar@oz.wsu.ukans.edu
ianhogg@cs.umn.edu (Ian J. Hogg) (06/21/91)
In article <1991Jun17.113108.168@wsuiar.wsu.ukans.edu> mnjafar@wsuiar.wsu.ukans.edu writes: >My company is considering buying a C++ compiler, we are runing SCO/V3.2. >So far we have only contacted SCO and Zortech. Do any other vendors >support C++ for the SCO platform ? Has any of you guys out there used >either one of the above compilers, and what do you think of them ? >Any help will be appreciated. > >Mohammad Jafar >mnjafar@wsuiar.wsu.ukans.edu >jafar@oz.wsu.ukans.edu I just started using Zortech on Xenix. It appears to me that they do not want you to use normal everyday system calls. I am working on an application that needs to make calls to a DB library compiled with SCO cc. Added extern C's to the include files and compiled fine. Lots of unsatisfied externals when linking though. Stuff like msgsnd, semctl etc. I can't add the SCO c lib to the link path because I get duplicate entries for the startup code. I had to extract the necessary .o's from libc.a and put them into a separate lib. (I may just add them to Zortech's lib later). I also got a unresolved external for something name __fltused. It is defined in libcfp.a and appears to be a constant. So I compiled a c program consisting of just "const int _fltused=1;", added it to my lib and everything SEEMS to be working ok. Anyone know if what I did was OK? The pointof this rambling is that I don't really trust this compiler for anything other than programs compiled entirely with ztc. Also, their include files are lacking "sys/types.h" for example only has a definition for time_t (I think) and a warning to not use this file because stuff in it is not portable. The DB vendor has compiled cleanly with cfront on SCO platform. -- =============================================================================== Ian Hogg ianhogg@cs.umn.edu (612) 225-1401