#12985: Possible future issues with ECL build with unicode enabled
------------------------------------------------------------------+---------
Reporter: pcpa |
Owner: was
Type: enhancement |
Status: new
Priority: minor |
Milestone: sage-5.1
Component: interfaces |
Resolution:
Keywords: | Work
issues:
Report Upstream: Reported upstream. Developers deny it's a bug. |
Reviewers:
Authors: | Merged
in:
Dependencies: |
Stopgaps:
------------------------------------------------------------------+---------
Comment (by pcpa):
Replying to [comment:2 fbissey]:
> Actually just looking at the patch, you are just adding a conversion
layer, right?
Yes, and if the ecl is built without unicode support, it should be a minor
overhead noop, as it would attempt to convert a base string to a base
string :-)
There are some comments from Juan at
http://sourceforge.net/tracker/?func=detail&aid=3526370&group_id=30035&atid=398053
that may be of interest, about possible issues with unprotected lisp
objects.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12985#comment:3>
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.
