Hi Eric and Travis! I'm afraid I need more help. I looked at the FreeModuleHomset example, but I couldn't quite match it with my situation.
The database contains a bunch of "combinatorial collections", like Dyck words or graphs. I think these should be the objects of my category, so I guess FiniteEnumeratedSets is an excellent fit. I model this in two classes FindStatCollection and FindStatCollections. We then have a bunch of "combinatorial maps", that really are morphisms in the category above. Reading FreeModuleHomset, it would appear that following your suggestion, FindStatMaps should actually take two arguments, namely the domain and the codomain of the maps, right? (Instead of taking no arguments, as currently, which means it contains all morphisms.) @Travis: > I'd also perhaps not use a classcall on the morphism, but instead explicitly construct the Homset (parent) and from that, construct the corresponding element to simplify the class (and it's a natural interface). I must admit that I do not understand, but I hope I will once the above is clearer... Martin -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
