Hi Simon, Yes, that's what I meant. I see it as a problem because if you had a python variable x, it will be overwritten by the symbolic value.
Isuru On Wed, Mar 20, 2019, 4:25 AM Simon King <[email protected]> wrote: > Hi Isuru, > > On 2019-03-19, Isuru Fernando <[email protected]> wrote: > > If the sage preparser did something like, > > > > __tmp__ = SR.var("x, y"); __tmp_g__ = lambda x, y: > > symbolic_expression(x+y**Integer(2)).function(x,y); f = > __tmp_g__(*__tmp__) > > > > for > > > > f(x, y) = x + y ** 2 > > > > you wouldn't have this problem and it should be easy enough to change in > > the preparsesr. > > By "problem" you mean that f(x,y)=x+y^2 creates symbolic variables > called x and y? I don't think that's a problem, but a useful feature. > > Best regards, > Simon > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
