Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ucsd!sdcc6!sdcc8!cs178abu
From: cs178abu@sdcc8.ucsd.EDU (John Schultz)
Newsgroups: comp.sys.amiga
Subject: Re: Anyone seen a good Amiga Pascal lately ?  Why not Modula-2?
Message-ID: <823@sdcc8.ucsd.EDU>
Date: 19 Mar 88 19:58:56 GMT
References: <2688@crash.cts.com> <821@nuchat.UUCP>
Reply-To: cs178abu@sdcc8.ucsd.edu.UUCP (John Schultz)
Organization: University of California, San Diego
Lines: 21

In article <821@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
>Does the Benchmark compiler track changes to the .DEF module and recompile
>affected modules if you change it?

  I haven't tried it yet, but I believe that a version key is
is checked during compilation (import phase).  If the versions don't
match, an error message would be generated.  That's what happened
with TDI, and is part of the Modula-2 lang. def.  When a def module
is changed, all modules importing that def module must be
recompiled, but when the mod module is changed (the actual code;
this occurs more often), no recompilation is necessary for other
modules.
  Basically, only variables, types, and procedure prototypes
are in the def mods; they aren't changed very often.  Looks like a
make equivalent would be useful in that case... Do other M2
compilers have that feature? (wouldn't be too hard to do)
  Actually, the best method would be to recompile the offending
modules as they are imported. The user would then need to save those
newly modified modules (both defs & mods in some cases) to permanent
storage.  This could get kind of hairy... How would make handle it?

  John