🚀 go-pugleaf

In message <46jpt7$r2j@jobe.shell.portal.com> - cgdaney@shell.portal.com (Charl
es G Daney) writes:
|  
|  
|  
|   > well, I have this data that I am trying to move out of VX-REXX, so how
|   > else can I do it? Even if I allocate some memory, I'll still have to
|   > serialize access, right?
|   
|  It depends how you allocate the memory. If you use malloc, it is private
|  to each thread. The C library takes care of that. If you use DosAllocMem,
|  it all depends on whether the pointer is available to more than one
|  thread. If in fact several threads could access the memory, then you do
|  need some sort of serialization.
|   
|  Charles
|  http://www.quercus-sys.com

Is there anu advantage to doing things this way, rather than with the 
options in the lnk/def file? It seems to me that this must have been 
exactly why they enabled that in the first place. Each VX-REXX app
instance will only ever need the data in one thread (I hope), and in 
any case, they MUST have access to the same, synchronized data, which
is much more important than separating stuff out (right?).

          Carsten Whimster     bcrwhims@uwaterloo.ca
           EDM/2 Associate Editor and Book reviewer
            Team OS/2           POV-Panel/2 author
                 OS/2 and Internet consultant
      http://www.undergrad.math.uwaterloo.ca/~bcrwhims/