[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
## [Axiom-developer] coerce, cast, partial fractions

**From**: |
Tim Daly |

**Subject**: |
[Axiom-developer] coerce, cast, partial fractions |

**Date**: |
Thu, 9 Oct 2003 10:31:55 -0400 |

Bill,
re: coerce vs casting
I wouldn't equate coercions with type casting. First, type casting in
languages like C "reinterpret" the bits. Coercions reinterpret the
type and potentially rewrite the representation. Second, type casting
traditionally references the "top level type" whereas Axiom can reach
into the type tower and move an "internal" type (e.g. UP(x,INT) to
UP(x,FRAC INT)).
re: partial fractions
If I understand the partialFraction answer (perhaps I don't) the
result given is a partial fraction as far as Axiom is concerned.
Partial fractions work on the factored equation and it appears
that Axiom doesn't think it can factor the equation over the
target domain so the partial fraction uses the "fully factored"
value. The issue appears to be that the target domain chosen by
the interpreter is one in which there are no factors. Or perhaps
it is just a street-level bug :-)
Tim

**[Axiom-developer] coerce, cast, partial fractions**,
*Tim Daly* **<=**
**[Axiom-developer] Re: coerce, cast, partial fractions**, *Dylan Thurston*, `2003/10/09`
**[Axiom-developer] Re: coerce, cast, partial fractions**, *Tim Daly*, `2003/10/09`
**Re: [Axiom-developer] Re: coerce, cast, partial fractions**, *William Sit*, `2003/10/11`
**Re: [Axiom-developer] Re: coerce, cast, partial fractions**, *Dylan Thurston*, `2003/10/11`
**Re: [Axiom-developer] Re: coerce, cast, partial fractions**, *Tim Daly*, `2003/10/15`
**Re: [Axiom-developer] Re: coerce, cast, partial fractions**, *David MENTRE*, `2003/10/15`
**[Axiom-developer] literate programs**, *Tim Daly*, `2003/10/15`

**[Axiom-developer] CVS build broken? -- errortrap**, *Camm Maguire*, `2003/10/10`