Xref: utzoo comp.databases:2586 comp.lang.misc:2962 comp.software-eng:1548
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!spdcc!cspencer
From: cspencer@spdcc.COM (Cliff Spencer)
Newsgroups: comp.databases,comp.lang.misc,comp.software-eng
Subject: Re: need help choosing between INGRESS and PROGRESS
Keywords: INGRESS, PROGRESS
Message-ID: <3275@ursa-major.SPDCC.COM>
Date: 19 May 89 11:38:10 GMT
References: <985@resource.UUCP> <309@viusys.UUCP> <24295@agate.BERKELEY.EDU> <1932@ssc.UUCP>
Reply-To: cspencer@ursa-major.spdcc.COM (Cliff Spencer)
Distribution: na
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Lines: 11

In article <1932@ssc.UUCP> fyl@ssc.UUCP (Phil Hughes) writes:
>and you can do virtually anything in it.  The only limitation that I don't
>like is that there are no passed variables in call lists if you precompile
>the called module.  You can, however, pass stuff in global variables
>or compile at run time (or even build a new program and then run it all

This is the real pain in the butt about PROGRESS. It should be noted that along 
with the restriction on all arguments to other procedures being passed as 
globals, compiled code size is restricted to < 63K. This can lead to code
that is more contorted than need be. 
							-cliff