Newsgroups: comp.os.os2.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!unixg.ubc.ca!cheddar.ucs.ubc.ca!ballard
From: ballard@cheddar.ucs.ubc.ca (Alan Ballard)
Subject: Re: OS/2 C compiler
Message-ID: <1991Apr20.190744.6675@unixg.ubc.ca>
Keywords: OS/2 'C'
Sender: news@unixg.ubc.ca (Usenet News Maintenance)
Nntp-Posting-Host: cheddar.ucs.ubc.ca
Organization: Computing Services, University of British Columbia
References: <1581@integow.uucp>
Date: Sat, 20 Apr 1991 19:07:44 GMT

In article <1581@integow.uucp> hot@integow.uucp (Roland van Hout) writes:
>
>We are UNIX C programmers. We have the possibility to port some of our
>applications to OS/2 for a client. Is it possible to compile reentrant
>C programs to save memory or must we implement threads to simulate
>this capability.
1) All OS/2 code is reentrant.  If you are run  more than one copy of the 
   program, only one copy of the code is loaded.
2) If you want to share code among different applications, you create
   "dynamic link libraries" containing the code. 
3) Even if you did need to use threads, you don't need to implement them.
   OS/2 has built-in threads.
OS/2 does all this stuff much better than unix.
 
Alan Ballard                   | Internet: ballard@ucs.ubc.ca
University Computing Services  |   Bitnet: USERAB1@UBCMTSG
University of British Columbia |    Phone: 604-822-3074
Vancouver B.C. Canada V6R 1Z2  |      Fax: 604-822-5116