From: gvision@ntlworld.com   
      
   "Jud McCranie"  wrote in message   
   news:3io5t0hmumqe8m04vunt39ofjop0vef49p@4ax.com...   
   > On Wed, 29 Dec 2004 11:57:00 GMT, "Jason Burgon"   
   >  wrote:   
   >   
   > >That will not acheive anything as far a providing more space for data is   
   > >concerned.   
   >   
   > You can (in effect) get two segments of nearly 64KB each for global   
   > data.  Basically you are using the 64KB stack.   
      
   That is LOCAL stack space. It does not provide you with any more data   
   segment space. If it's not extra DS space, then why kludge it using the   
   stack - why not simply use the heap?   
      
   > >> The main program can have almost 64KB of data and the procedure can   
   > >>have almost 64KB of data.   
   > >   
   > >Wrong.   
   >   
   > I did it successfully many times...   
      
   You mean you wrote many kludged programs using inappropriate, large and   
   slow-to-access nested local variables, or did your programs consist of one   
   monolithic procedure? Apart from the poor programming ethics of such an   
   approach, have you ever checked the code produced by the compiler when a   
   nested procedure  has to access a local variable of one of its parent   
   procedures?   
      
   --   
   Jay   
      
   Author of Graphic Vision   
   http://homepage.ntlworld.com/gvision/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)