Profile-Compiler: constant expressions optimizations about brouter HOT 6 OPEN

Would the "second level" catch this?

No. I thought about detecting such assigned variables that are effectively unused, but that's difficult because there's also this remote access from the node context to the way-context ( "add way:townpenalty .." ) and it's hard to cover each edge-case so better keep it simple..

from brouter.

@abrensch
OK, I saw it. And will start with that. But in the next few weeks my time is a bit limited.

from brouter.

OK, I saw it. And will start with that. But in the next few weeks my time is a bit limited.

Sorry, assignig to you was just by accident. I will look into it, but commit via merge request and welcome a review by you. It's easy to introduce subtle bugs. When looking into the code, I already realized there might by a glitch with numerically evaluated tags not leading to marking the tag as "used".

from brouter.

I add a small new logic for global expressions.
Please see my repo profile-compiler
It removes the unused tags from messages list.

from brouter.

I created a merge request for my patch: #573

from brouter.

Would the "second level" catch this?

assign townpenalty
    switch estimated_town_class=   switch highway=residential 1.5 1.0
    switch estimated_town_class=1  1.5
    switch estimated_town_class=2  1.8
    switch estimated_town_class=3  2.4
    switch estimated_town_class=4  2.6
    switch estimated_town_class=5  2.8
    switch estimated_town_class=6  3.0 1

assign costfactor
    multiply switch consider_towns townpenalty 1
    ...

from brouter.