Martin,
Without trying to solve the more general problem of rationalizing
InputForm and unparse in FriCAS, attached is a patch to 'axiom.py'
(relative to sage-3.1.2 + Mike's patches (trac_4036.patch
trac_4036-2.patch trac_4036-3.patch trac_4036-fixes.patch)) that
solves the problem of parsing '
Martin,
> The only slight awkwardness I can imagine is as follows: If I export, say, in
> Polynomial
>
> coefficientRing: () -> Ring
>
> then the result of baseRing will be a Ring, and may have "forgotten" all the
> other categories it possibly satisfies. Hm, it seems I will never understand
>
(question for Ralf at the bottom of the mail :-)
"Mike Hansen" <[EMAIL PROTECTED]> writes:
> >> * Given a domain like "Polynomial Integer", how do I get the base ring
> >> "Integer" programatically? This would be like the base_ring method in
> >> Sage.
> >
> > You cannot, currently. One possibi
Mike,
Here is another function to add to axiom.py:
def compile(self,code, filename="temp.spad", verbose=False):
"""
Compiles a library module written in spad
EXAMPLES:
sage: axiom.compile('''
)abbrev package FOO foo
Foo():with
Mike,
Here's a minor issue with your patch to axiom.py.
I noticed that you included a hack for Axiom function names with ? and
! suffixes. As you know Sage/Python does not permit these characters
in identifiers. The Axiom convention is that functions with names
ending in ? return True or False a
Hello,
> A float, once computed, is insensitive to "digits". I don't think it even
> knows it's precision, but that should be very easy to change.
Being able to figure out how many bits of precision a particular Float
has would be useful.
>> * Given a domain like "Polynomial Integer", how do I
