Hi

I found a place in the code which only dealt with a single OR.  Changing
that to deal with any number seems to fix the problem.

There is however a problem that a test fails.  It does not appear to
be directly related to the fix, since it only occurs when resolving
the same way with different (changed) tags against the same
rule set.  That needs more investigation.

Patch attached, and jar here: 
http://files.mkgmap.org.uk/download/247/mkgmap.jar

> as A drian pointed out here:
>
> http://gis.19327.n5.nabble.com/Bug-in-handling-of-bus-stops-tp5832099.html
>
> we have a bug in the style evaluation system. The attached patch
> makes sure that each rule is only evaluated once for one element.
> If I got it right the problem occurs with rules that combine two
> "or" expressions, like
> (a | b) & ( c |  d) { do something }
>
> A binary based on r3436 is here:
> |http://files.mkgmap.org.uk/download/244/mkgmap.jar
> |
> @Steve: Please review, I've added a new field "matched" to
> WatchableTypeResult
> but I think the field "found" was  already intended for this?
> Maybe you find a better place to fix this?
>
> Gerd
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>