From 870f00bb36f5af3088344371764da48bbde9651a Mon Sep 17 00:00:00 2001
From: Christian Hesse <mail@eworm.de>
Date: Thu, 3 Jan 2019 17:45:43 +0100
Subject: global: variable names are CamelCase

            ___  _         ___     __
           / _ )(_)__ _   / _/__ _/ /_
          / _  / / _ `/  / _/ _ `/ __/
         /____/_/\_, /  /_/ \_,_/\__/
 _       __     /___/       _             __
| |     / /___ __________  (_)___  ____ _/ /
| | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ /
| |/ |/ / /_/ / /  / / / / / / / / /_/ /_/
|__/|__/\__,_/_/  /_/ /_/_/_/ /_/\__, (_)
                                /____/

RouterOS has some odd behavior when it comes to variable names. Let's
have a look at the interfaces:

[admin@MikroTik] > / interface print where name=en1
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
 0  RS en1                                 ether            1500  1598

That looks ok. Now we use a script:

{ :local interface "en1";
  / interface print where name=$interface; }

And the result...

[admin@MikroTik] > { :local interface "en1";
{...   / interface print where name=$interface; }
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
 0  RS en1                                 ether            1500  1598

... still looks ok.
We make a little modification to the script:

{ :local name "en1";
  / interface print where name=$name; }

And the result:

[admin@MikroTik] > { :local name "en1";
{...   / interface print where name=$name; }
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU
 0  RS en1                                 ether            1500  1598
 1   S en2                                 ether            1500  1598
 2   S en3                                 ether            1500  1598
 3   S en4                                 ether            1500  1598
 4   S en5                                 ether            1500  1598
 5  R  br-local                            bridge           1500  1598

Ups! The filter has no effect!
That happens whenever the variable name ($name) matches the property
name (name=).

And another modification:

{ :local type "en1";
  / interface print where name=$type; }

And the result:

[admin@MikroTik] > { :local type "en1";
{...   / interface print where name=$type; }
Flags: D - dynamic, X - disabled, R - running, S - slave
 #     NAME                                TYPE       ACTUAL-MTU L2MTU

Ups! Nothing?
Even if the variable name ($type) matches whatever property name (type=)
things go wrong.

The answer from MikroTik support (in Ticket#2019010222000454):

> This is how scripting works in RouterOS and we will not fix it.

To get around this we use variable names in CamelCase. Let's hope
Mikrotik never ever introduces property names in CamelCase...

*fingers crossed*
---
 mode-button-scheduler | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'mode-button-scheduler')

diff --git a/mode-button-scheduler b/mode-button-scheduler
index 4d3facf..bce6089 100644
--- a/mode-button-scheduler
+++ b/mode-button-scheduler
@@ -4,15 +4,15 @@
 #
 # act on multiple mode-botton presses from scheduler
 
-:global "mode-button";
+:global ModeButton;
 
-:local count ($"mode-button"->"count");
-:local code ($"mode-button"->[ :tostr $count ]);
-:local parsed [ :parse $code ];
+:local Count ($ModeButton->"count");
+:local Code ($ModeButton->[ :tostr $Count ]);
+:local Parsed [ :parse $Code ];
 
-:set ($"mode-button"->"count") 0;
+:set ($ModeButton->"count") 0;
 / system scheduler remove mode-button-scheduler;
 
-:log info ("Acting on " . $count . " mode-button presses: " . $code);
+:log info ("Acting on " . $Count . " mode-button presses: " . $Code);
 :delay 1s;
-$parsed;
+$Parsed;
-- 
cgit v1.2.3-54-g00ecf