From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_MSGID, SUBJ_ALL_CAPS autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9e20292f693f1408 X-Google-Attributes: gid103376,public From: mw@ipx2.rz.uni-mannheim.de (Marc Wachowitz) Subject: Re: ADA CORE TECHNOLOGIES ANNOUNCES GNAT-TO-JAVA SYSTEM Date: 1997/09/20 Message-ID: <6008fe$9lm$2@trumpet.uni-mannheim.de>#1/1 X-Deja-AN: 274049779 Organization: --- Newsgroups: comp.lang.ada Date: 1997-09-20T00:00:00+00:00 List-Id: ok@goanna.cs.rmit.edu.au (Richard A. O'Keefe) wrote: > Slim binaries are based on two ideas: > - source code compresses very well > - IO is slow. To be practical, it's also important that compile time is reasonably small for acceptably good code; a compiler must not use too much resources, as it's part of the system. Some slim-binary-systems do also use post-optimization at run time (possibly adapting to the empirical system behaviour), after having generated relatively simple and slow code on loading. It surely helps that Oberon(-2), the language for which slim binaries have been developed, is extremely simple and straight-forward to compile, and as integrated part of the Oberon operating system or a browser, it tends to stay around between different programs. I'm not sure whether the same concept would work well for stand-alone programs in much more complicated (for the compiler) languages. -- Marc Wachowitz