#21062: How to store information on codes build from other ones
---------------------------------+------------------------
Reporter: jlavauzelle | Owner:
Type: task | Status: new
Priority: major | Milestone: sage-7.3
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+------------------------
Comment (by dlucas):
Hello Julien,
Thanks for writing this!
I think it's indeed a good idea to think about this, and I can't either
imagine a `DualCode` class.
Elaborating a bit on your structure, -well, that's what we discussed a few
hours ago `;)`- I think we could implement a new decorator whose purpose
would be to store the operations you describe in the `_derivation_tree`.
With such a decorator, it will be extremely easy to set a new
"transformation" method in the framework: just decorate this method, and
every time it's called, the decorator takes care of building the tree from
the input of your new "transformation" method.
It's the first idea that came to my mind, and is of course open to
discussion!
David
--
Ticket URL: <https://trac.sagemath.org/ticket/21062#comment:2>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
