[Coco] getenv bug in cgfx explanation
lothan at newsguy.com
Sat Dec 12 12:50:12 EST 2009
From: "Gene Heskett" <gene.heskett at verizon.net>
> As for your comment re there being 3 copies of the mouse in there, I would
> suspect they are all identical, and this is caused by c.link only making
> pass over the library(s) looking for dependencies. Because it is
> to predict backward dependency's, I have been forced to add 2nd copies of
> stuff in the libraries I built back then myself, trig.l in particular.
> we should redo c.link to make another pass, say up to 3, over all the
> libraries given if at the eof of the current pass, there are still un-
> resolved dependencies? (Note, it will make more passes if the library to
> linked from is named more than once too) If after 3 passes it hasn't been
> found, it likely is a real error and never will be, report it and die.
I wonder if there's sufficient memory to build a dependency tree in the
first pass. If so, this can be safely reduced to a two-pass link step: build
the dependency tree in the first pass, merge the dependency trees (thereby
removing modules that aren't needed by the mainline), followed by pulling
out the dependencies from the .lib files in the second pass.
More information about the Coco