From: "Nick Roberts" <Nick.Roberts@dial.pipex.com>
Subject: GNAT Error Reporting
Date: 1999/02/18
Date: 1999-02-18T00:00:00+00:00 [thread overview]
Message-ID: <7ahkn2$kab$2@plug.news.pipex.net> (raw)
Well, I can vouch for the sophistication of GNAT's (3.11) error reporting,
anyway. I have only been trying it out for a short time, but it evidently
does indeed produce clear, simple messages, and suggests (usually perfectly
accurately) how to fix the error. Great! I give credit where it is due :-)
For my own compiler, I shall try to provide similarly useful messages and
suggestions. In addition, I fancy trying to put in the following features:
(a) a utility to facilitate the tailoring of the text of error messages (to
different languages, different target audiences, etc.);
(b) an interactive facility which progressively suggests 'fixes' to a
problem (most likely first);
(c) the ability for the user to choose a suggested fix, and have that fix
applied to the source text automatically;
(d) maybe a way of graphically relating error parameters to the source text
(something like little red boxes and arrows).
These are just ideas. There seem (to me) to be a lot of possibilities. Is
there any literature specifically on this subject available?
-------------------------------------
Nick Roberts
'The time has come,' the Walrus said,
'To talk of many things:
Of shoes--of ships--and sealing wax--
Of cabbages--and kings--
And why the sea is boiling hot--
And whether pigs have wings.'
Lewis Carroll
"Through the Looking Glass"
-------------------------------------
next reply other threads:[~1999-02-18 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-18 0:00 Nick Roberts [this message]
1999-02-18 0:00 ` GNAT Error Reporting dennison
1999-02-18 0:00 ` robert_dewar
1999-02-18 0:00 ` robert_dewar
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox