Prev: Taskbar Icon - No Effect When Some Child Windows Display.
Next: DTPicker and bolding dates
From: Dean Earley on 18 Jun 2008 05:53
boris wrote:
> "Christian ASTOR" <castorix(a)club-internet.fr> wrote in message
> news:05f79d52-4d4e-4d32-8da4-9e85e5900540(a)b1g2000hsg.googlegroups.com...
>> On 23 mai, 10:38, "boris" <some...(a)nowhere.net> wrote:
>>> PIDs (Process IDs) are unsigned int32 in Windows.
>>> But in reality I've never seen PIDs > (max unsigned int16).
>>> Is PID generation algorithm documented anywhere?
>>
>> The PID is just the index of the new entry in the PID handle table
>> (linked list)
>>
> I see. Thanks.

You shouldn't rely on anything that appears to be coincidental.
You may have noticed that PIDs are also (currently) divisible by 4...
http://blogs.msdn.com/oldnewthing/archive/2008/06/06/8576557.aspx

Specifically:
> I wish to emphasize that the behavior you see in Windows NT-based kernels is just an implementation artifact which can change at any time.


--
Dean Earley (dean.earley(a)icode.co.uk)
i-Catcher Development Team

iCode Systems
 | 
Pages: 1
Prev: Taskbar Icon - No Effect When Some Child Windows Display.
Next: DTPicker and bolding dates