🚀 go-pugleaf

In article <UWGST3y00WA9I2PlIm@andrew.cmu.edu> rs4u+@andrew.cmu.edu (Richard Siegel) writes:
>
>At any rate, I noticed that a considerable amount of compilation
>time is taken sucking the source files for units in a USES clause
>from disk, and the following occurred to me: Suppose, if after
>a successful compilation, the compiler were to write a .Dump
>file to disk? The .Dump file would contain the symbol tables

The $LOAD mechanism does avoid rereading the interfaces.  If the $LOAD file
exists, it is read instead of the textual interfaces, otherwise the text
files are read and the $LOAD file is created.

The main problem with $LOAD file is that you have to use a $LOAD file in the
same context in each compilation.  The information in the $LOAD file depends
on the units it includes as well as the units preceeding it in the USES
statement.  (Some of these issue will be addressed in MPW 3.0, and this
whole mechanism will be much more automatic and streamlined.)

Using $LOAD speeds up the compilation significantly, although it still is
much slower than LSP.

-- 
		 Larry Rosenstein,  Object Specialist
 Apple Computer, Inc.  20525 Mariani Ave, MS 32E  Cupertino, CA 95014
	    AppleLink:Rosenstein1    domain:lsr@Apple.COM
		UUCP:{sun,voder,nsc,decwrl}!apple!lsr