On 07/26/2011 09:51 AM, Malcolm Herring wrote:
On 25/07/2011 19:41, Paul Hartmann wrote:
I'd call it a missing feature. There is no != or =~ operator for eval
expressions [1]. You can work around the first limitation like this:
I was not using it within an eval expression, but with the
On 26/07/2011 09:54, Paul Hartmann wrote:
Anyway, would be good to have 'set' implemented, as well. I still don't
know what it does exactly, though. E.g. can you write something like this?
*[religion][religion!=christian][religion!=jewish] {
set religion=INT-generic;
}
Operators such as != =~ cause parsing errors if they are used following
an eval() expression. Only = is accepted. Is this a bug or a feature?
___
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev
