Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!capmkt.UUCP!tim
From: tim@capmkt.UUCP
Newsgroups: comp.windows.news
Subject: Re:  C Client arrays
Message-ID: <8903062209.AA03521@bill.capmkt.com>
Date: 7 Mar 89 01:41:51 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29


ppgbms!moe!paul@philabs.philips.com writes:

>>One *VERY* big problem with this method is that the array data is being
>>put on the stack of the server side liteweight process, so if you're
>>trying to pass an array bigger than 1000 words, look out for a stack
>>overflow!  (I've heard there is a way to increase the stack size, but
>>have never found out how).

there is apparently a  workaround for this.  after i had posted the original
method, a fellow from sun (i believe it was <owen@sun.com> but i have lost the
original message) sent me tip saying that if you use executable arrays, then the
stack is not used at all. so changing the code to read

cdef arraystart()
  { %%% instead of [

cdef arrayend()
  } %%% instead of ]

should solve the stack-overflow problem.  if anyone understands the magic behind
this, i would be interested in knowing how/why this works.

tim edwards
capital market technology, inc.
1995 university, #390
berkeley, ca   (415)540-6400

tim@capmkt.com or capmkt!tim@uunet.uu.net