Improve column number when reporting MapCSS parsing error

[naoliv]

It took me a lot of time to debug something like this:

*[highway][highway !~ /motorway_junction|bus_stop/][ref][ref !~ /foo/bar|something/] {
        throwWarning: tr("foo");
}

With JOSM saying:

ERRO: org.openstreetmap.josm.gui.mappaint.mapcss.parsergen.ParseException: Encountered " "!" "! "" at line 1, column 62.

column 62 is is the ! from the last ref but actually the problem is that I have an unnescaped / in this test (foo\/bar)
Could the parser give a more precise column number when this happens?

[bastiK]

This is as good as it gets, sorry. Making syntax error messages more human comprehensible is an insanely difficult task, certainly the man hours required are in no relation relation to the possible improvement.

[naoliv]

Right, I understand. Thanks!