RE: Win32 port survey results
[email protected] ("Moore, Paul")
| Newsgroups | perl.loop |
|---|---|
| Message-ID | <714DFA46B9BBD0119CD000805FC1F53BDC3A6F@UKRUX002.rundc.uk.origin-it.com> |
From: Nick Ing-Simmons [mailto:[email protected]] > > It does not mention that in the book I have - is your source > either empirical or definitive ? MSDN - does that count as apocryphal? :-) From the documentation of MsgWaitForMultipleObjects() Parameters: nCount Specifies the number of object handles in the array pointed to by pHandles. The maximum number of object handles is MAXIMUM_WAIT_OBJECTS minus one. Plus, \VisualStudio\VC98\Include\WINNT.H:#define MAXIMUM_WAIT_OBJECTS 64 // Maximum number of wait objects The book I first saw this in said 32 - 64 is better, but still a hard limit... From: Joshua > What does Microsoft recommend? Is the use of threads manditory? AFAIK, Microsoft don't recommend anything. I presume the normal usage would involve threads, but even then, I'm not sure how I would write things which were both generic and scalable :-( As I don't use Event in anger, could I ask the assembled company - how much use would an implementation which was limited by this be in practice? Paul.