{at}SUBJECT:Re: DosAllocThreadLocalMemory()                             N
MSGID: 3:633/379.0 2f372b52

 -=> Quoting Russell Coker to All <=-



 RC> I have just read about the DosAllocThreadLocalMemory() API call.

 RC> I wonder what the purpose of this is and whether the documentation on

 RC> it is correct.  The documentation states that up to 32 DWORDs of

 RC> memory may be allocated.  32DWORD == 128 bytes which is a lot less

 RC> than the page size...  Is this 128 bytes allocated in the same page as

 RC> the TIB or something? Also what is the use of it?  What is the

 RC> benefit of DosAllocThreadLocalMemory() over having CHAR LocMem[128] in

 RC> the thread function?  Why would anyone bother with a special system

 RC> call to get 128 bytes of local memory when using the stack is so much

 RC> easier?



I have not looked into it but there would be use for a function similar to
what this one sounds like.



What I would like to see is to be able to allocate a small amount (but I
can't see why this should be forced) of memory for which I can later on
retrieve the address (I identify some sort of identifier).  This would have
little use for applications but simplify writing certain API calls I have
written a lot.  The 'handle' allows any number of independant pieces of
code to all have their own per thread data.





--- Blue Wave/Max v2.12 OS/2 [NR]

632/103 301 341 348 633/379 635/503 711/409 PATH: 633/379 632/348