🚀 go-pugleaf

Oh yes, still about "real product" development - probably the tool
we miss most is a real LINKER - something like the PLINK product for
MSDOS, or just about any good old Unix LD - something that will NOT
barf and/or die when you throw at it a couple of megabytes worth of
executable to build out of a few thousand routines (each in its own
segment, I believe - we have to thank the HUGE memory model for
that).  With the Microsoft linker, we are at the level where we can
just barely link everything "plain", but if for example we take just
one routine out of a library and try to add it to the link as an obj
(say to test a modification to it without adding it to the lib yet)
we overflow some critical internal table (instead of giving the
error messages intended for this case it goes crazy and fingerpoints
to the compiler... but just put the obj into the lib and the link
goes OK, so we know the compiler is a scapegoat here!).  Any advice
would be appreciated.
-- 

Alex Martelli - Email: staff@cadlab.sublink.org, alex@am.sublink.org
Phone: ++39 (51) 371099, ++39 (51) 250434; fax: ++39 (51) 366964