🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.os2.programmer
4 messages
4 total messages Started by Roland van Hout Fri, 19 Apr 1991 13:46
OS/2 C compiler
#2560
Author: Roland van Hout
Date: Fri, 19 Apr 1991 13:46
11 lines
881 bytes
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.

-- 
UUCP: ..!uunet!mcsun!hp4nl!integow!hot	or  hot@integow.UUCP 
Roland van Hout, Sr. software engineer, Integrity software consultants, 
         Pelmolenlaan 2, 3447 GW Woerden, Netherlands,
            tel +31 3480-30131, fax +31 3480-30182
Re: OS/2 C compiler
#2562
Author: Alan Ballard
Date: Sat, 20 Apr 1991 19:07
18 lines
1502 bytes
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
Re: OS/2 C compiler
#2564
Author: Mikael Wahlgren
Date: Sun, 21 Apr 1991 08:35
8 lines
947 bytes
In article <1991Apr20.190744.6675@unixg.ubc.ca> ballard@cheddar.ucs.ubc.ca (Alan Ballard) writes:

>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.

Note that some C-libraries are NOT reentrant.

Mikael Wahlgren      d9mikael@dtek.chalmers.se
Re: OS/2 C compiler
#2565
Author: Alan Ballard
Date: Sun, 21 Apr 1991 17:29
14 lines
1477 bytes
In article <1991Apr21.083505.22743@mathrt0.math.chalmers.se> d9mikael@dtek.chalmers.se (Mikael Wahlgren) writes:
>
>Note that some C-libraries are NOT reentrant.
>
All the C libraries handle reentrancy across processes, as far as I know
(they have "instance data" allocated for each process).  However, it
is possible to have problems with multiple threads because there isn't
a separate copy of this data for each thread.  For example, a static I/O
buffer can cause problems if two threadsin the same process do I/O. 
There is a multi-thread version of the standard library to deal with this. 
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
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads