🚀 go-pugleaf

    My usual strategy for passing data to threads is to use malloc'd
memory. It seems that in C Set++, at least, memory can be malloc'd by
one thread and later freed by another with no ill effects (whether this
is guaranteed behavior I have no idea; anyone?), i.e.

void foo(int magicNumber)
{
    int *ip;

    ip = malloc(sizeof(int)); // SHuold checkfor failure here.
    *ip = magic_number;

    _beginthread(myThread, NULL, 4096L, ip);
}

void myThread(void *intPtr)
{
    int magicNumber = *((int *)(intPtr));

    free(intPtr);

    ...

    _endthread();
}

    This way you never have to worry about another thread stomping on
your data. Just be sure that the child thread frees the memory when it
is done.

    By the way, if all you want is to pass an integer, you can just
typecast the last parameter, like so:

void foo(int magicNumber)
{
    _beginthread(myThread, NULL, 4096L, (void *)magicNumber);
}

void myThread(void *intPtr)
{
    int magicNumber = (int)intPtr;

    ...

    _endthread();
}

This is of course pretty evil, and relies on
sizeof(int) <= sizeof(void *), which you should at least put into an
assert if you use this particular hack.

--
    Kevin