On Mon, Mar 27, 2000 at 03:33:22PM +0100, "Nick Ing-Simmons" wrote:
> Paul Moore <[EMAIL PROTECTED]> writes:
> >PS I have just noted a worrying point in the MsgWaitForMultipleObjects
> >documentation. It seems that the maximum number of objects which can be
> >waited on is about 32.
> It does not mention that in the book I have - is your source either
> empirical or definitive ?
According to my version of MS C++:
#define STATUS_WAIT_0 ((DWORD )0x00000000L)
#define STATUS_ABANDONED_WAIT_0 ((DWORD )0x00000080L)
80L - 00L = 128
So maximum it could be is 128. The 32? I dunno about that... This limit
may not exist with WAIT_ALL=TRUE, but that would defeat the purpose of
doing the wait in the first place... (NOTE: This doesn't limit us from
using separate threads to do separate waits... although I dunno how far
to take that...)
> >This doesn't seem like a lot to me - is it likely to
> >be an issue (do select() and/or poll() have similar limits?)
They do not.
mark
--
[EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | SIR Tools (7H12)
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | Nortel Networks
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
