On Friday, August 8, 2014 8:10:32 PM UTC+1, Simon King wrote: > > metaclass that combines a given class Foo with methods inherited from > parent classes of categories does exactly the same.
Not quite, metaclasses don't have to use the inheritance crutch to combine the actual class read from the library with a dynamic class. You can just generate any class you want directly, with the method layout that you want. Therefore I believe it is honest (and less confusing) to give > it a new name, since it is *not* Foo. Having a class name that is nowhere in the sources appear out of nothing is utterly confusing. John has quite some experience developing Sage. It would of course be less confusing to have the actual name shown, duh. Right now you can only figure this thing out by reading the category source code, and it is often not a pretty sight. -- 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.
