> On Tue, 22 Jan 2008, Nick Alexander wrote: > >>> I would like to establish some (roughly) like this: If a > >>> computation cannot be > >>> expressed from the command line (in pure Python) then it cannot be > >>> a standard > >>> part of Sage. E.g. if you cannot compute $sin(x)$ for some $x$ > >>> from the > >>> command line but you can do it by clicking some Java buttons, then > >>> this > >>> functionality would not be considered a part of (standard) Sage. > >>> > >>> Would that make sense? > >>> Martin
There is something I don't get: it seems like JSON is going to be used by clients to simply send or receive data from SAGE. What the client does with the result of the computation is its problem. Why do we have to worry about testing this at all? > The interface itself might be tricky -- however, the communication protocol > isn't hard to test, whatever computations go on behind the scenes aren't hard > to test, and Java has some *great* unit-testing capabilities, so that side > isn't hard to test either. In short, there is very little that we wouldn't > be able to test in an automated way. > And what is there to test? That the data is well-formed? didier --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
