Zugg Software :: View topic - [3.19f]BUG: Multiple var.key syntaxes in #SWITCH now broken

Posted: Thu Jun 17, 2010 2:19 am

1. Untitled session.
2. On command line, type testdb.test="true"
3. On command line, type #SWITCH (@testdb.test="true") {#SAY {This is true.}}. It should fire 'This is true.' in the main window.
4. Now type #SWITCH (@testdb.test="true") {#SAY {This is true.}} (@testdb.test="false") {#SAY {This is false.}}. This fires an illegal character in expression of . (this is referring to the SECOND @testdb.test, as verified by making an alias in settings editor with the same line.
5. Further testing: #SWITCH (@testdb.test) ("true") {#SAY {This is true.}} ("false") {#SAY {This is false.}} returns properly again.

While I realize that step 5 is the optimal way to do it, the bug still presents problems for a.) people who have not converted to that format yet and b.) people who have a predetermined order of #IFs in which they use different database variables throughout the #SWITCH or c.) cases where people are doing #FORALL something {#SWITCH (%i>@var.key)}.

Charneus

Posted: Thu Jun 17, 2010 4:27 pm

Confirmed and added to bug list. Still working with some special cases in the parser dealing with the varname.key syntax, so that must have broken this.