Because mjtnet disallows creating a new thread, I add one here with Subject titled "Assigned Bug"
ASSIGNED does work for variable names with %%
Let>i=1
Let>j=1
Assigned>Item%i%_%j%,x
Let>Item%i%_%j%=123
Let>Item1_1=123
Assigned>Item%i%_%j%,y
MDL>y
Y will be False even though it has already been assigned with 123.
Assigned Bug
Moderators: JRL, Dorian (MJT support)
-
Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Erm - this IS a new thread?
Assigned works only with simple non-embedded variables.
Assigned works only with simple non-embedded variables.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
I should have removed: Because mjtnet disallows creating a new thread, I add one here with Subject titled "Assigned Bug."
Sorry for my oversight. My fault.
Thanks for confirming Assigned>'s peculiar limitation.
Then, nonetheless, how could we decide if an embedded/paramterized variable is undefined?
Let>i=1
Let>j=1
MDL>x_%i%_%j%
In the above script, MS gently display 'x_1_1' even though it was undefined. I discover an interesting feature of MS: When an variable is undefined, it's treated by MS as a char string.
Sorry for my oversight. My fault.
Thanks for confirming Assigned>'s peculiar limitation.
Then, nonetheless, how could we decide if an embedded/paramterized variable is undefined?
Let>i=1
Let>j=1
MDL>x_%i%_%j%
In the above script, MS gently display 'x_1_1' even though it was undefined. I discover an interesting feature of MS: When an variable is undefined, it's treated by MS as a char string.
