Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!uflorida!mephisto!mcnc!rti!mozart!walker
From: walker@unx.sas.com (Doug Walker)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice/SAS C  5.10 HERE!
Message-ID: <1990Aug30.153659.9434@unx.sas.com>
Date: 30 Aug 90 15:36:59 GMT
References: <14874@shlump.nac.dec.com> <1990Aug24.173432.13867@cs.umn.edu> <1990Aug24.185241.18275@nada.kth.se>
Organization: SAS Institute Inc.
Lines: 20

In article <1990Aug24.185241.18275@nada.kth.se> d88-skl@dront.nada.kth.se (Stellan Klebom) writes:
>I just wonder why is it so hard for people who managed to create a compiler,
>that is actually doing a good job, to make the macro expansion buffer dynamic?
>Since there is a option to set it's size then it must be malloc'd anyway!
>To me this seems like a fairly easy thing to remove all sofware restrictions
>from, and just letting available memory space set the limit.

In 5.10 it is malloc'd, but only once (at the beginning).  If we provide for
reallocating it, we would have to locate every place that has a pointer
into the buffer and change the pointers to point into the new buffer.  This
would be possible, but we judged it too risky for the 5.10 release and 
delayed it until 6.0.  


  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: ...mcnc!rti!sas!walker   plink: dwalker  bix: djwalker