#20039: Subfield subcodes
-------------------------------------+-------------------------------------
       Reporter:  dlucas             |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-7.1
      Component:  coding theory      |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  David Lucas        |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/dlucas/subfield_subcode          |  3b172ad13fd4782b80049897fa046254cecaf01c
   Dependencies:  #19930, #19653     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by dlucas):

 Hello,

 I did that for consistency with the new code classes I'm designing, in
 which the base field of the code is the first argument.
 I'd prefer to do so, as I like when all the classes of a library have the
 same calling conventions (if possible, of course).

 And in that case, it was actually done in #19930... Which is now closed.
 I deprecated the old convention, of course.

 I hope it's not a problem...

 Best,

 David

--
Ticket URL: <http://trac.sagemath.org/ticket/20039#comment:11>
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.

Reply via email to