Martin R wrote:
> 
> Because of limited time I can only make a rather short comment:
> 
> it is easiest to make the sage interface work with a representation (I used 
> InputForm) that allows you to recreate the object in FriCAS.

Well, there is one representation that allows you to recreate
the object in FriCAS: used by history command and for storing data
in files.  But I do not think it is easy to use for interfacing.
 
> In other words, a domain "GeneralForm" that drops some of the information 
> is *not* useful.
> 
> The reason is, that with a non-lossy representation (what I hoped InputForm 
> would become eventually), the maintainer of the sage interface can decide 
> how to translate a given object into the type hierarchy of sage.

IMO trying to represent all FriCAS data in Sage in does not
make much sense: if you want all just define mapping from
FriCAS types to Sage types by reading .daase to know what
is available and generate wrappers/interface routines on
Sage side.  That way you can anything by sequence of
appropriate calls.

>  I think 
> it is necessary that the interface is part of sage, because new types are 
> added to sage on a weekly basis, and, in principle, the conversion from 
> FriCAS types could take advantage of this.  A relatively recent example 
> might be the skew polynomial ring.
> 
> I'm afraid that FriCAS does not have the human resources to provide an up 
> to date interface.

Well, there are a lot of interesting things to do in FriCAS.
Interfacing work is comparatively less interesting.  And past
interest in the interface was rather low -- I would say
ratio of quality of interface to interest was high enough
so that I can not justify investing extra effort in Sage interface.
To put if differently: if there is no pull on Sage side to use
FriCAS I am not going to push.

-- 
                              Waldek Hebisch

-- 
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to fricas-devel+unsubscr...@googlegroups.com.
To post to this group, send email to fricas-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/fricas-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to