Post Reply 
Why x:=CAS("x") = 0 ?
03-28-2018, 02:47 AM
Post: #3
RE: Why x:=CAS("x") = 0 ?
It is an assignment in the same line of LOCAL, I would understand it if it were:
LOCAL x;
x:=CAS("x");
But this could also be possible:
LOCAL var1:=var1; → var1=0 ??

I do not really agree that it fails like that.

Regarding the double environment generated by CAS CAS, it seems to me that it is not working as expected, now it can be exploited but will should continue searching until it leaves the final nested environment?

Viga C | TD | FB
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Why x:=CAS("x") = 0 ? - Carlos295pz - 03-27-2018, 12:52 PM
RE: Why x:=CAS("x") = 0 ? - Han - 03-27-2018, 02:24 PM
RE: Why x:=CAS("x") = 0 ? - Carlos295pz - 03-28-2018 02:47 AM
RE: Why x:=CAS("x") = 0 ? - Carlos295pz - 03-28-2018, 03:21 AM
RE: Why x:=CAS("x") = 0 ? - Carlos295pz - 03-29-2018, 11:14 AM



User(s) browsing this thread: 1 Guest(s)