2019



On Oct 29, 2019, at 11:03 AM, Scott @ Itsula <scott@itsula.co.uk> wrote:






Evaluates strings prior to numbers?



 





From: <=a href=3D"mailto:iphonzie@gmail.com" style=3D"color: rgb(149, 79, 114); tex=t-decoration: underline;" class=3D"">Brian Fries
Sent: 2=9 October 2019 17:59
To: WebDNA Talk
Subject: [WebDNA] IF statement evaluation bug report, WebDNA 8.5.1





 







I=92ve identified a bug with IF statement evaluation. My se=tup:







Product: WebDNA - Enterprise Edition
Version: 8.5.1
Platform: unix-Macintosh OS X
Server OS: macOS 10.12.6 (16G2016)







Also tested on:
Product: WebDNA - Enterprise Edition
Version: 8.5.1
Platform: unix-Macintosh OS X
Server OS: macOS 10.14.6 (18G87)







And on:





Product: WebDNA (FastCGI)
Version: 8.5.1
Platform: linux unix 64bits
Server OS: Ubuntu 14.04.5 LTS













I can code around the bug, so I don=92t need suggestions fo=r other ways to achieve my goals, I=92m just reporting inconsistent and inc=orrect behavior by WebDNA.







My code was testing for the presence of a page parameter wh=ich should either not be present or should have a numeric value greater tha=n zero, depending on how the user got to the page:











[if ([pParam]>0)][then=]



* Got good parameter



[/then][else]

* No parameter, or i=nvalid parameter



[/else][/if]











This worked fine, until I added an additional expression to= the IF statement:











[text]list=3Done,two,thre=e[/text]



[if ("[list]"^&=quot;one") & ([pParam]>0)][then]







TRUE * Got good parameter=







[/then][else]





FALSE * No parameter=, or invalid parameter, or list does not contain =93one"





[/else][/if]











This example ALWAYS goes to the TRUE clause, unless the fir=st expression fails. Whether the second expression is TRUE or FALSE doesn==92t matter.







For debugging, I simplified the components until I got to t=his, which incorrectly executes the TRUE clause:











[if (2=3D2=) & (ABC>0)][then]



TRUE
[/then][else]
FALSE
[/else][/if]







Testing the individual expressions, they both work correctly. (2=3D2) execu=tes the TRUE clause, while (ABC>0) executes the FALSE clause:











[if (2=3D2)][then]=



TRUE



[/then][else]

FALSE



[/else][/if]







[if (ABC&g=t;0)][then]



TRUE



[/then][else]

FALSE



[/else][/if]










Interestingly, switching the order of the expressions, corr=ectly evaluates to the FALSE clause:










[if (ABC>0) & (2=3D=2)][then]
TRUE
[/then][else]
FALSE
[/else][/if]














Thanks,



Brian Fries










--------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing listtalk@webdna.us To unsubscr=ibe, E-mail to:talk-leave@webdna.us= archives:http://www=..webdna.us/page.dna?numero=3D55 Bug Reporting:support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list= talk@webdna.us To unsubscribe, E-mail to: =tal=k-leave@webdna.us archives: =http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us