On Tuesday, March 11, 2014 6:21:19 PM UTC-4, Nicolas M. Thiéry wrote: > > On Mon, Mar 10, 2014 at 11:36:01AM -0700, Niles Johnson wrote: >
> > After scanning the ticket discussion and documentation, I > > think the purpose is to provide some way of mixing in some (but > > not all) methods from one class to another. And it is desirable > > that these be "top-level" methods -- that makes sense too. > > Hmm, I am not sure to see what you mean. See below too. > I think I was trying to understand what practical thing an axiom accomplishes, and I thought it was basically just a way of letting certain methods from instances of class A be called from instances of class B. But it's more than that . . . > > For me, an axiom A is just a predicate on the objects of the category > Cs() defining it. Then, for each subcategory Ds() of Cs(), you can > consider the full subcategory Ds().A() of the objects of Ds satisfying > the axiom. And, if relevant, implement that category to provide > methods for those objects and their elements. > Thanks for clarifying. -Niles -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
