Hi Paul,

You wrote me:

 PE> If you ignore recursion,

I do. There is no recursive function involved. Sri, i forgot to tell you.

 PE> the maximum amount of stack size you can use is to have every single
 PE> function get called, in one big chain, in which case, the stack size is
 PE> the sum of all the local variables in all your functions. Normally, this
 PE> will be vast overkill.

Ok, but it yields a sufficient amount of stack.

 PE> If your source is in multiple files (hence multiple object code),

The program has the following structure:

===================================
standard header files
main
functions
include yet another bunch of functions
===================================

It does not matter whether i include these functions manually in the editor
or let the C compiler do the trick. It is one .obj file in either case.

 PE> Much easier to allow the user to specify the stack size!

Using an iterative method to determine the approximate stack size. :-(

 PE> icc /B"/stack:50000" fred.c

That works. The reason why i'm amazed is that Unix can determine the
correct or a sufficiently large amount of stack, and OS/2 seemingly can't.
I thought i might have been forgotten a compiler switch...


73 es cuagn,
 Henk

--- GoldED 2.50+