#17721: variable shadowing: major design flaw in Singular
-------------------------+-------------------------------------------------
Reporter: | Owner:
jakobkroeker | Status: new
Type: defect | Milestone: sage-6.5
Priority: major | Keywords: Singular
Component: packages: | Authors:
standard | Report Upstream: Reported upstream. Developers
Merged in: | acknowledge bug.
Reviewers: | Branch:
Work issues: | Dependencies:
Commit: |
Stopgaps: todo |
-------------------------+-------------------------------------------------
Singular has an issue of overlapping namespaces
where variable conflicts will lead to bugs without warnings:
{{{
//Singular code:
ring rng = 0, p ,dp;
poly p = p^2 - p - 1; // **boom**
p; // ( p = -1, wrong ! )
}}}
In combination with hardcoded variable names or unreflected usage of
'execute' in Singular's library code this may lead to wrong results as
shown in
http://www.singular.uni-kl.de:8002/trac/ticket/677.
See also:
the discussion at http://www.singular.uni-
kl.de/forum/viewtopic.php?f=10&t=2482
Main upstream ticket:
http://www.singular.uni-kl.de:8002/trac/ticket/684
Trying to translate the example from http://www.singular.uni-
kl.de:8002/trac/ticket/677 to sage
I hit another bug (#17720)
--
Ticket URL: <http://trac.sagemath.org/ticket/17721>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
