Hi, Sorry for sending my e-mail without subject by mistake to sage-devel. I think that your first solution would be much better I think it would be nicer to make lcalc a library with a nice api, rather than a program only unsable from the command line. (with this design the program would call the library )
Pablo On 5/29/09, r Rishikesh <rishi...@gmail.com> wrote: > > I have a patch which is working (thanks to mabshoff for helping me > remove the horrible memory leak in Tucson). The patch does not have > doctests. It relies on a patch to lcalc itself. I have asked Mike > Rubinstein to make it a part of lcalc. This was more than 2 months > ago. I have not heard anything from him since then. Within the next > week I will post the patches and the documentation. > > There is a reason why patches to lcalc are necessary. > > For example, the function which computes zeros of an L-function spits > it out with a cout . I added a patch to lcalc which adds > functionality to return the zeros in a vector<double>. This can be > converted to python list of sage RealField(). > > The other solution I thought was to write to a temporary file and read > from there. I doubt it will be any better than current use of pexpect. > Only advantage would be that for computing with arbitrary L function > (satisfying the conditions lcalc requires) will become possible. > > Rishi > > On May 28, 11:58 pm, Pablo De Napoli <pden...@gmail.com> wrote: >> Hi, >> I want to ask about the status of wrapping lcalc library >> (ticket #5396) >> I would be interested in helping with that, but there is no patch yet. >> >> Pablo > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
