[m-dev.] delaying compile errors until runtime

[Fergus Henderson]

On 23-Dec-1999, Mark Anthony BROWN <dougl at cs.mu.OZ.AU> wrote:
> schachte at cs.mu.OZ.AU writes:
> > 
> > On 22 Dec, Fergus Henderson wrote:
> > > It might be nice to add an option to the Mercury compiler
> > > that would cause it to go ahead and generate executable
> > > code anyway, even if compile errors were found.  The generated
> > > code would then raise exceptions at runtime, if/when it was
> > > executed.
> 
> Sounds OK.  Presumably the compiler would still report the errors
> (or maybe turn them into warnings).

Yes.  The compiler would still report them as errors, i.e.
starting with "Error:", but it would return a zero exit status
(indicating success) so that Mmake would still go ahead and
link the executable even if such errors were encountered.

> I think the use of this
> option should generate a warning, regardless of whether any compile
> errors were found.  It's also probably worth generating a warning
> any time such code is called, like we do for obsolete predicates.

Hmm, I'm so sure about the merits of these.  I think they might
end up just being noise rather than useful information.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------