Feature strings with no quote in BT XML policy#150
Conversation
Signed-off-by: Marco Lampacrescia <marco.lampacrescia@de.bosch.com>
Signed-off-by: Marco Lampacrescia <marco.lampacrescia@de.bosch.com>
Signed-off-by: Marco Lampacrescia <marco.lampacrescia@de.bosch.com>
Signed-off-by: Marco Lampacrescia <marco.lampacrescia@de.bosch.com>
Signed-off-by: Marco Lampacrescia <marco.lampacrescia@de.bosch.com>
| <bt_tick target="initial"> | ||
| <!-- In a Reactive sequence, if another node fails we should reset this... --> | ||
| <if cond="waiting == false"> <!-- TODO: support !waiting later on--> | ||
| <if cond="!waiting"> |
|
@MarcoLm993 @ct2034 I think this change broke AS2FM compilation/verification with Scan. Now strings are not surrounded by single quotes in SCXML either, and are thus interpreted as identifiers (the outer double quotes belong to the XML syntax, while everything inside them is interpreted as ECMAScript). I am unsure about the rationale for this change, but at least I would like to recover the previous behavior for the SCXML output. Other than that, are you sure the change could not cause similar issues elsewhere? How is a string literal distinguished by an identifier in general? |
@EnricoGhiorzi Oh, I did not notice that the SCXML part got broken: |
|
Thank you @MarcoLm993 fir the reply, it is now clear why this was necessary. It seems indeed that the issue is limited to string literals originating from the BT. Please, let me know if any help is needed. |
With this change, we do not need to wrap strings in the BT.xml ports with single quotes.
If strings contain quotes, they will be considered part of the string itself (via escaping).
This means
BT Port = "'aaa'"->ASCXML data = "'\'aaa\''"