Hi Travis, Thanks for your suggestion! I'll experiment with it later today.
Also, if you're not really using matrices, such as doing a significant > number of multiplications/using category model/etc., but instead as a nice > data structure, I'd be more inclined to say to strip out the non > speed-essential methods, making it as lightweight and specific as possible > and converting to proper matrices when needed, and include it into sage > (after perhaps changing the name). How does this sound to everyone? > That is, in fact, what we've done. The class LeanMatrix and its subclasses only implement the essential (to us) operations, using cdef methods for speed. They are only used internally: the user inputs Sage matrices, and whenever the code returns a matrix, it's a Sage matrix (some advanced, underscored, methods are an exception, but those are mainly for internal use). --Stefan. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
