raph@info.ucl.ac.be (Raphael Collet) writes:
> An experienced user, having a look at the code and the error message,
> understands that the compiler had considered the expression X,Y as a
> nested object application. However, everyone should agree that the
> compiler error messages must signal errors AND give some hints to the
> programmer in order to understand where the bug comes from. I think
> nobody would complain if the message was a bit more explicit, like:
>
> In nested object application: X,Y
>
> the message must contain exactly one nesting marker.
The only addition you are suggesting is to remind to people
what an object application is. Oz is not that big a
language - I believe we can expect from our users that
they learn its full syntax. Or that they look up the term
`object application' that occurs in the error message in
the online documentation. It's not that hard!
> Of course, it is said that the problem is at "line 4, column 11", but I
> personally never navigate in a program *only* by looking at line and
> column number. We could be much more productive if the compiler gives
> us more visual hints in error messages.
Obviously you are unaware of Emacs support for jumping to
these exact coordinates with a single command: next-error
(bound to C-x `). This helps a _lot_! Then you get the
*original* source and not something mangled by the compiler.
> PS: I won't propose myself for improving the error messages :-) I am
> currently in lack of time. Sorry.
That's a pity. Aren't we all?
Leif.
-
Please send submissions to hackers@mozart-oz.org
and administriva mail to hackers-request@mozart-oz.org.
The Mozart Oz web site is at http://www.mozart-oz.org/.