[m-dev.] preferences for error contexts

Julien Fischer juliensf at csse.unimelb.edu.au
Fri May 15 17:33:47 AEST 2009


On Fri, 15 May 2009, Mark Brown wrote:

> On 15-May-2009, Paul Bone <pbone at csse.unimelb.edu.au> wrote:
>> On Fri, May 15, 2009 at 04:04:47PM +1000, Ralph Becket wrote:
>>> Paul Bone, Friday, 15 May 2009:
>>>>
>>>> I use the tool 'error' which takes the error output of mmc or some other
>>>> compiler and adds the errors as source code comments to the relevant parts of
>>>> my source files.  This will break with the new format, as in the example above
>>>> only the text "In clause for" would be added to my source file.
>>>
>>> Surely 'error' can't be more than a few lines of Awk?
>>
>> ~pbone/bin/error is compiled from error.m which comes from somewhere in the
>> mercury CVS repository.
>>
>> Why does it matter?
>>
>
> This would have been written because the standard `error' program does
> not handle mercury error messages, presumably.  If this is the case,
> there is little point keeping the current form of messages.  I vote we
> always produce errors in the proposed format, and distribute our error
> program as part of Mercury.

It is distributed as part of the extras distribution; I take it you mean
with the core system instead?

Julien.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the developers mailing list