🚀 go-pugleaf

<>
<This was originally E-mailed out as a response to a posting by duts!bhs00.
 However, since it got returned to me, and might be of interest to others
 here, I'm taking the liberty of posting it.>


   Thanks for the info on where to find the Atari Technical Users Notes.

   As for your Deep Blue C problems... well, I recently purchased Deep Blue C,
and frankly, it's lacking in several respects.  First and foremost, it is *not*
a true compiler.  It "compiles" into pseudo-code, which is subsequently 
translated for execution at runtime.  My admittedly non-exhaustive testing has
shown that it's maybe 20% faster than interpreted Basic, and the generated
command files take up a lot more disk space (I don't have the figures with me).
Another large problem (why the .COM files are so large) is that the linker
doesn't use libraries; if a file is listed in the .LNK file, the entire
thing gets thrown in, even if you're only using one of the functions.
   As chairman of the local Atari User's Group languages SIG, I have just
embarked upon the odyssey of attempting to write a "true" Small-C compiler,
complete with relocating linker featuring library management.  Now, it may be
that I come to the conclusion the J. H. Palevich did (i.e. it's not
possible, given diskspace and memory constraints), but I'll learn a lot
trying.  If you have any suggestions, comments, etc., let me know.

 - Joel Plutchak
   {allegra,ihnp4,seismo}!uwvax!uwmacc!oyster