>>> I think it's just about getting people to fix it. There are many >>> people around who can fix Python/Cython and a little less (I guess) >>> who can fix C++ and C. But a lot less who can fix lisp. > > As I mentioned before, another big > problem is that lisp doesn't manipulate native Python objects efficiently. > Python *is* just a C library -- Python and C/C++ play very well together, > especially because of Cython. The same is not the case with lisp/maxima.
Actually, I think even just couple years ago, even though Python was written in C, it was a *pain* to call it from C easily. Yes, a lot of people did it, but it was a pain. Maybe that's the situation in lisp, surely some implementation is written in C and maybe it's possible to call it from C (and pass pointers around). But imho noone is seriously using it. In Python all of this has changed due to Cython, that many many people use in production now, so again, big thanks to the whole Sage community who helped to bring pyrex to production. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
