[m-dev.] Odd error from the compiler

Peter Moulder Peter.Moulder at infotech.monash.edu.au
Wed Jun 18 18:42:01 AEST 2003


On Mon, Jun 16, 2003 at 12:18:11PM +1000, Ralph Becket wrote:

> I never introduced a variable called TypeInfo_39 and I don't know why
> the compiler failed to ensure it was instantiated at that point (of
> course, I could go wading around the compiler internals, but I think
> that would be asking a bit much of most users.)

Could a "normal" user work it out by looking at --dump-hlds <something>
output?  Would it be reasonable for error messages mentioning
compiler-introduced variables to suggest that the user look at that?

> Something that told me what I'd done wrong!

Of course I agree that would be better in the longer term, or if it can
be done easily.  Mercury compiler error messages are sometimes quite
daunting at the moment.  Addressing this may be valuable for getting
Mercury taught to undergrads or perhaps more generally for attracting
new users.  It isn't near the top of my own wishlist, FWIW.

pjm.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------



More information about the developers mailing list