I'm not sure that fricas *has* to be a package : the current versins (6.4, 6.5beta) already have the fricas interface compiled in :
/usr/local/sage-6.5/src/build/lib.linux-x86_64-2.7/sage/interfaces/fricas.py /usr/local/sage-6.5/src/sage/interfaces/fricas.py /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.py /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.pyc and fricas() calls a possible systemwide fricas. Successfully. Therefore fricas has the same "Sage status" as Mathematica, Magma or Matlab. However, the fricas interface lacks a .fricas() method for getting the (a) fricas-palatable representation of some objects. It also lacks somethong to avid the "ascii_art" default output of fricas, which is quite unparsable by the sage() method (which exists). I also saw somewhere on the list the suggestion of a "algorithm=fricas" option to integrate(), which seems a very good idea. Nevertheless, having a fricas package which might replace a systemwide fricas installation might help its disemination. HTH, -- Emmanuel Charpentier Le samedi 6 décembre 2014 18:23:32 UTC+1, vdelecroix a écrit : > > Hello, > > I just discover FriCAS and its tremendous possibilities. I just updated > the package that we ship we Sage from version 0.3.1 to version 1.2.4 (more > information at http://trac.sagemath.org/ticket/9465). It might become a > more standard package. > > I have a very naive question: the version of lisp we have in Sage is ecl, > does it make a huge difference with sbcl ? > > Best > Vincent > -- 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. For more options, visit https://groups.google.com/d/optout.
