[antlr-interest] ANTLR 3.0.1: invalid character column in a mismatch character error message.

[Brent Yates]

I use SlickEdit and it wants line:column.  Before that I used CodeWright and
it also wanted line:column.  In both cases the first line and first column
is 1.  I am currently adding an ANTLR driven parser to SlickEdit to handle
Verilog and I have to track tabs manually (for error messages) since the
ANTLR lexer does not.  I have not seen an editor that wants line:char
offset, but I'm sure they exist.

byates

On Wed, Aug 13, 2008 at 5:05 PM, Foust <javafoust at gmail.com> wrote:

> Gavin wrote:
> > You still need to give line/column information,
> > so that IDEs can jump straight to the location of
> > the error themselves.  (I'm assuming here that
> > the IDE is separate from ANTLR and can't access
> > its internal structures -- and most IDEs expect
> > errors to have a line:column format.)
>
> Is that true? The popular IDEs don't take line + character offset?
>
> If so, then you have a compelling argument to add Tab translation support.
> You may, anyway. But with regard to what IDEs expect, it's difficult to
> believe that they'd want anything other than the line# and raw number of
> characters from the beginning of the line. Do you think C++ compilers are
> really doing character -> column# translations (with Tab translation)
> before
> outputting syntax errors?
>
> Brent
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20080813/7abf36a8/attachment.html