On Jul 8, 2009, at 4:46 PM, David Roe wrote: > Discussion: we currently have CategoryObject._base as a C attribute > because some elements want fast access to a "base." Is > CategoryObject the right place to put this? Maybe we should > generalize the examples of sage.rings.integer_mod.NativeIntStruct > and sage.rings.padics.pow_computer.PowComputer_class?
I think it may be useful to have an extra object field for stuff like NativeIntStruct and PowComputer_class. However, base is so common that we might as well stick it there and make it easy to access. > > > * Currently ParentGens.__init__ does not call > ParentWithBase.__init__. This should presumably change at some point. I believe both of those should simply go away when everything's moved to the new coercion model. - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
