[Oberon] Modula2 vs Oberon IMPORT

[Duke Normandin]

On Sat, 8 Jan 2011, Jan Verhoeven wrote:

> On Saturday 08 January 2011 21:40:07 Duke Normandin wrote:
> > "one incarnation of every procedure used" => OK makes sense
> > "nothing more" => meaning no other un-used procedures from the
> > IMPORTed modules, or meaning no 2nd or 3rd etc copy of used
> > procedures?
>

> It's all a bit immaterial. If you want tight code, use assembler or
> Forth.  If you want to program in a safe language with a rather wide
> comfort zone, use Oberon or Modula-2 (in FQI mode).

[snip]

> The obc generates Oberon byte code that is 75% tighter than Modula-2
> machine code and runs equally fast.

Obviously, from your data above, it's possible to work with a language
compiler that is both safe, and does not suffer from code bloat "by
design". Not all compilers are the same. BTW, I have no problems with
using FQI. I was merely concerned about including every bloody
procedure in every module that happened to be referenced in the IMPORT
statement.
-- 
Duke