commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <>
Subject Re: [jelly] error reporting
Date Wed, 22 Jan 2003 15:36:12 GMT
From: "Paul Libbrecht" <>
> file.jelly:linenum:colnum: comment

I've implemented the above, but with the element name of the tag that caused
the error

foo.jelly:100:23: <foo> some comment

How's that?

All these fields are available on the JellyException, so you can always
format them however you wish.

----- Original Message -----
From: "Paul Libbrecht" <>
To: "Jakarta Commons Users List" <>
Sent: Wednesday, January 22, 2003 3:09 PM
Subject: Re: [jelly] error reporting

Le mercredi, 22 jan 2003, à 15:46 Europe/Paris, Christian Sell a écrit :
> 1. unknown core tags are simply ignored, the body is evaluated and the
> tag is written to stdout. Shouldnt there better be an exception
> instead?

I think this may already be a bug. If not, it >>HAS TO<< to be one.
I do believe that anything in a given namespace should be provided by
the tag-library which should in most of the cases throw an error.

> 2. error messages (e.g., when exceptions occur) are written in a
> format that shows the line information at the very end of a usually
> rather long line. Shouldnt this better be something like
> file.jelly [22:3] - some error occurred
> or at least easily configurable.

I think the official format. That of javac at least, should be
file.jelly:linenum: comment
more comments
or (that of jikes)
file.jelly:linenum:colnum: comment
more comments

Also, it would be nice that error reporting doesn't always include a
stacktrace, for example it could be an option of the Jelly command-line
class. It would make things somewhat more compact and would help us
detect possibly extraneous output...


To unsubscribe, e-mail:
For additional commands, e-mail:

Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts

View raw message