Ok, I agree that it would be nice for all derived cones to share the base cached data. How about Cone() just stores all of its cached data in a hash self.shared_cache (or so) instead of in self. For the computer thats essentially the same as what you are suggesting, but in the implementation you wouldn't need to fiddle with __getattr__ and would keep an inheritance chain like
Cone -> Cone_of_fan Cone_of_toric_variety -> Cone_of_codomain Even if the implementation details are not important to the user, I think it would help with the future maintenance. On May 21, 5:13 pm, Andrey Novoseltsev <novos...@gmail.com> wrote: > I especially worry about cone/fan computations that trigger calls to > associated lattice polytopes and polyhedra In the long run we should write a cython module that does the basic cone/polyhedron operations instead of parsing palp or cdd output. That said, I've looked at the palp source code and I'm certain only Max understands what it does. I think writing something new based on the Parma Polyhedral Library (C++) is the way to go. > Some other comments: > define functions like is_Cone(cone) Yes, definitely nice syntactic sugar. > Did you do any work on your module for toric lattices since the > version posted here:http://www.stp.dias.ie/~vbraun/Sage/? No, I haven't made any changes. > I saw that you have some interface to get triangulations from TOPCOM. The main problem right now is that TOPCOM segfaults when checking regularity (=coherence). But I think that I can fix that quickly. The interface I have written works for everything else, though. You probably shouldn't spend much time implementing some subdivision algorithm in python. Volker -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
