[mkgmap-dev] Not-equal compare bug?

Sat Jan 5 08:13:10 GMT 2019

Hi Ralf,

yes, I think this is a bug. In opposite to the previously posted rules your rules should work.
@Steve: If I got that right the ExpressionArranger kicks in too early. It should only be called when the if-stack is empty (again).
Can you have a look at it?

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ralf Kleineisel <ralf at kleineisel.de>
Gesendet: Freitag, 4. Januar 2019 22:00
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Not-equal compare bug?

On 1/3/19 1:35 PM, Harri Suomalainen wrote:

> Do I missunderstand something or is this a bug?

I think it's a bug.

The same problem occurs with the "if .. then" syntax:

This works:

if (railway=*) then
  if (tunnel=yes) then
    ()                {delete railway}
  else
    railway=rail      [0x14 resolution 21]
    railway=tram      [0x14 resolution 22]
end

This does not:

if (railway=*) then
  if (tunnel!=yes) then
    railway=rail      [0x14 resolution 21]
    railway=tram      [0x14 resolution 22]
  end
end

"Error in style: Error: (lines:196): Invalid rule expression: $tunnel!=yes"

This also does not work:

if (railway=* & tunnel!=yes) then
    railway=rail      [0x14 resolution 21]
    railway=tram      [0x14 resolution 22]
end

You cannot use the "!=" test in "if .. then" syntax at all as far as I
can tell.
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev