Golam Mortuza Hossain wrote: > Thanks Minh and Robert, > > On Mar 18, 8:28 pm, Robert Bradshaw <rober...@math.washington.edu> > wrote: >> This is because (f)(x) calls f at x rather than performing >> multiplication. It is for exactly this kind of reason that we're >> deprecating the "call without explicit arguments" behavior. > > OK, now I understand the underlying reason for the weird behaviour. > > Is there a way in Sage, to turn-on something like "Strict Mode" where > Sage will raise an error or at least a warning for such situation ( > "call without explicit arguments") ? > > To me, it seems to be a really serious issue as it affects the > reliability of > of the answers from Sage (specially for a long symbolic calculation). >
That's what Robert is saying. There is a patch that is undergoing revision right now that deprecates this behavior. That means that for the next little while, there will be a warning anytime this happens. Eventually, this functionality will be removed. Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---