|
Can we no longer use "or | || and & &&" in expressions?
Issue Type: |
Status: |
Priority: |
Date Submitted: |
Votes: |
Bug |
No Longer Required |
High |
Mon 2nd Jan 2012 |
1 vote
|
|
Found in version: |
Last Updated: |
Completed in version: |
Date Completed: |
Track Changes: |
5.0.22 |
Sun 3rd Aug 2014 |
5.0.32 |
Sun 3rd Aug 2014 |
Log In |
|
ElliotM | | Mon 2nd Jan 2012 05:17 |
I've been attempted to bug fix one of my projects for a couple hours now and have narrowed down one problem to 'bad expressions' whenever I attempted to use AND or OR in building test cases for If().
From the Adrift 4 manual:
If "test" evaluates true, returns x, else returns y
Where "test" is a=b, a==b, a<b, a<=b, a>b, a>=b, a<>b, a!=b
and conditions can be ANDed using "and", "&" or "&&"
or ORed using "or", "|", "||" |
|
ElliotM | | Mon 2nd Jan 2012 06:01 |
Hmm, I've now produced one that worked fine with an "or" but I still have others which seem to fail. |
|
ElliotM | | Thu 5th Jan 2012 23:16 |
I may have been mixing integer and string condition tests in an If(), and I believe I've heard that those aren't currently allowed? I was trying something fairly complicated, so the failure may have been due to something else. |
|
Campbell | | Mon 16th Jul 2012 15:15 |
Can you send me an example of what was giving you an error? |
|
ElliotM | | Mon 16th Jul 2012 15:52 |
Its been so long and I had several versions of that project, so I'm not sure I remember what I was trying to do. I'll see what I can do. |
|
ElliotM | | Sun 3rd Aug 2014 03:46 |
Lets go ahead and mark this as closed as I can use these symbols just fine with what I'm doing currently. |
|
Campbell | | Sun 3rd Aug 2014 11:10 |
Ok, great, thanks. |
|