#4126: [with patch; not ready for review] improve sage <--> magma interface for
number fields
-------------------------+--------------------------------------------------
Reporter: was | Owner: was
Type: enhancement | Status: new
Priority: minor | Milestone: sage-3.1.3
Component: interfaces | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by was):
The part 3 patch that I applied does some re-architect-ing of the sage -->
magma conversion system so now one can define either _magma_init_ in the
very simple case when a pure string is enough or _magma_coerce_ when one
wants to do arbitrarily complicated stuff but doesn't want to have to
worry about caching.
Caching turns out to be extremely important, e.g., coercing the same
number field twice into magma without caching would result in two separate
copies of that number field in Magma with no coercion maps, which would
cause lots of problems for other things. This re-architecting will surely
be needed all over the place as the Magma / Sage interface gets steadily
improved.
It's possible that the choices of names is not optimal. Using
_magma_coerce_ was better than anything else I could think of (e.g.,
_magma_not_cached_, _magma_impl_, etc.).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4126#comment:1>
SAGE <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
