Subj : Re: pthreads-win32 question...
To   : comp.programming.threads
From : David Schwartz
Date : Thu Feb 10 2005 04:47 pm


"Randy Howard" <randyhoward@FOOverizonBAR.net> wrote in message 
news:MPG.1c75b23da0d2f380989f8e@news.verizon.net...

>>     Stack operations are inherently non-portable. One could even concieve 
>> of
>> a conforming implementation that didn't have a stack.

> I don't disagree, however, my understanding is if 
> _POSIX_THREAD_ATTR_STACKSIZE
> is defined by the implementation, then not only does it have a stack, but 
> you
> have some degree of control over it with the appropriate pthread 
> functions.

    Except there's no portable way to know how much stack space anything 
takes.

> It seems to me that if it does have it, then having either the minimum 
> stack
> size, or the current stack size be zero on that platform is 
> counterintuitive.

    Yeah, but not non-conforming. There is no portable way to know what a 
particular size means or how much stack space is needed for anything.

    DS

.