CR> Make the stack as large as you have to--there is no serious disadvantage
CR> within reasonable limits. You should have some idea what you are doing
CR> that is gobbling up stack space. Are you using a lot of very large
CR> arrays as automatic data objects? Are you using recursive functions?
no, but this program does have a lot of objects of classes.. private data
members aren't kept on the stack, are they? It seemed the more _code_ I
added, the more stack space was needed. Boosting the stack space to 32k has
cured all the "mysterious" problems I was having compiling this thing for
DOS. Thanks for your help!
--- Maximus/2 3.01
---------------
* Origin: CYBERSPACE/2 þ Kingston, Ont þ 14.4 & 33.6 (1:249/117) (1:249/119)
|