#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
Reporter: mpatel | Owner: drkirkby
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.5.2
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by SimonKing):
Replying to [comment:34 drkirkby]:
> However, if I understand correctly, 4.5.2 is going to be library updates
only, with no updates to .spkg files, so I do not believe an updated
Singular.spkg is likely to be merged in 4.5.2, though it might if the
update is seen as critical. Though changing variable names in one version,
when another version is likely to be merged on the release after this, is
perhaps not a great idea.
Is it really "changning variable names"? If I understood correctly,
Singular does not use the variable name {{{mu}}} - it consistently uses
{{{Kstd1_mu}}}, and so do I. So, I wouldn't call it "changing variable
names" but "clearifying a variable definition".
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:36>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
