[Patch] MapCSS parser: skip all whitespace

[simon04]

In order to resolve the limitation "JOSM MapCSS is not liberal with white spaces in the selector…" from wiki:Help/Styles/MapCSSImplementation, we could ignore whitespaces at the lexing phase, i.e., by using the JavaCC SKIP keyword …

With this modification, also [highway ! = footway] would be parsed correctly (note the space between ! and =). To get around this, one would have to combine <EXCLAMATION> <EQUAL> into one token like it is done for <PIPE_Z>.

Is there a special reason, why whitespace handling is done in each grammar rule separately?

[bastiK]

Also from the wiki:

But, if we were to write it like this (with white space between the object type and the tests), it would not parse:

 relation [type=route]
   way [highway]

The idea behind this is strict compliance with the CSS standard:

p.info {

}

matches a paragraph <p class="info">, but

p .info {

}

matches elements inside a paragraph with class info, e.g. <p>x<span class="info">y</span></p>.
This means that white space cannot be ignored because it makes a descendant selector.

Now MapCSS is not the same as CSS, but the idea was to use the CSS standard, unless there is a reason not to.

In this case, the reason would be, that it is just easier if you can put white-space anywhere. But this argument doesn't convince me. :)

[simon04]

hm, right. I didn't think of that – let's keep it as it is. :-)