#17973: Better Sage consistency for naming and calling in linear_code
-----------------------------+----------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.6
Component: coding theory | Keywords:
Merged in: | Authors:
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies:
Stopgaps: |
-----------------------------+----------------------------
Some method and parameter names in linear_code.py file are abbreviated
names which might be confusing (for instance the `distance` parameter
actually stands for the minimum distance).
Most importantly, the `gen_mat` method will be renamed `generator_matrix`
and the `check_mat` method `parity_check_matrix`.
Besides, some getter methods to access the private fields of linear codes
exist but are not used internally in the class.
To support subclassing, it is better to use these instead of directly
invoking a parameter.
--
Ticket URL: <http://trac.sagemath.org/ticket/17973>
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.