TIP: Click on subject to list as thread! ANSI
echo: os2prog
to: Russell Coker
from: Dennis Bareis
date: 1995-02-05 11:43:06
subject: Re: DosAllocThreadLocalMemory()

-=> 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]

* Origin: Bunyip's Cave - Melbourne, Australia (3:633/379)
SEEN-BY: 12/2442 620/243 624/50 632/103 301 341 348 633/379 635/503 640/820
SEEN-BY: 690/660 711/409 410 413 430 807 808 809 934 942 949 955 712/515
SEEN-BY: 713/888 800/1 7877/2809
@PATH: 633/379 632/348 711/409 808 809 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.