On Aug 29, 2008, at 5:07 AM, Robert Bradshaw wrote:

> On Aug 29, 2008, at 5:01 AM, John Cremona wrote:
>
>> The trouble was that I wanted common code for both additive and
>> multiplicative groups, which I can -- almost-- implement.  Your way,
>> we have one type of element derived from some MultiplicativeElement
>> class and another from an Additive one, with a lot of duplicated  
>> code.
>
> OK, I think I understand your question better then. In that case, I
> think the right approach is to define a wrapper class that provides a
> multiplicative interface to a additive group (and vice-versa). A
> tight wrapper in Cython would be very little overhead, and I think
> this would allow for a lot of code re-use.

See http://trac.sagemath.org/sage_trac/ticket/3999

- Robert


--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to