Waldek,
I cannot really judge this patch since I have no idea what the arguments
of mmCost0 actually are. But it really looks like an ad-hoc patch.
Go on if you think it solves the problem. But you should definitely add
some documentation to i-funsel.boot of why you do this, otherwise it
will just add complexity that nobody understands anymore in the future.
Since you refer to
>
http://sourceforge.net/tracker/?func=detail&aid=2974970&group_id=200168&atid=972421
you seem to want to avoid coercion of 2 to 2...@float. Am I wrong?
I guess, digamma(2.0) should still give 0.42278433509846725.
Looks like only the interpreter is the problem, no change for compiled
code, right?
What you do in
isApproximate(t) ==
op := CAR(t)
member(op, ["Float", "DoubleFloat"]) => true
member(op, ["Complex", "Expression", "List", "Polynomial",
"Matrix", "Vector"]) => isApproximate(CAR(CDR(t)))
false
looks like defining a new Category "Approximate", putting Float and
DoubleFloat in it and having this category (conditionally) inherited by
the other constructors you list above. Only that you do this in the
above function without categories.
Since I consider the category way more flexible, I'd like to ask, how
complete your list of the above domain constructors is.
Please, put at least the URL to this email thread into the code.
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
