[m-dev.] for review: trailing for the MLDS back-end

[Robert Jeschofnik]

On 13-Dec-2000, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:

> I changed the behaviour for nondet pragma c_code so that
> rather than calling error/1, it instead generates code
> which calls error/1.  With that change, and others
> described below, I can build the compiler in grade
> hlc.gc.tr and pass the tests in extras/trailed_update.

Perhaps it would be good if the compiler also gave a warning in this case?
That way the user knows that there are problems before running their program.

It would seem a little undesirable to me to only learn of an
error/unimplemented feature/whatever at run time, after the compiler exited
without giving any hints as to what will happen. This could be especially bad
if the code in question was only run in the users program under very rare
circumstances...

This also shouldn't hinder bootchecking, unless there are nondet pragma
foreig_code's in the compiler, which I am going to guess that there are not.



just a thought,
Rob
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------