Macro call result depends on macro order

0 votes
asked Apr 15 in Bug by PMH
Hello.

There are two examples of code. The first one:

@startuml
!define test(x) test##x
!define test2(x) test(x)

A -> B: test(TestString)
A -> B: test2(TestString)
@enduml

test2 works incorrectly.

The second example with another rows' order works correctly:

@startuml
!define test2(x) test(x)
!define test(x) test##x

A -> B: test(TestString)
A -> B: test2(TestString)
@enduml

So, in the first example param x was handled like a string "x", but in the second example all worked correctly.

Is it a bug?

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:

[Antispam2 Feature: please please wait 1 or 2 minutes (this message will disappear) before pressing the button otherwise it will fail](--------)
To avoid this verification in future, please log in or register.
...