CAS: (2^10)! is undefined?

[sasa]

Look at wikipedia, bug is a wide range of reasons caused improper software functionality:
https://en.wikipedia.org/wiki/Software_bug

But I will not talk about semantic, that is not important at all...

I considered it as a minor bug, as anyone would expected "overflow" error instead "undefined". Since you did not implemented the overflow/underflow mechanism which was mandatory, that may be quite bigger problem which probably require core redesigning, which is often not naive at all...

Also there is no difference in logic regarding handling operation failures, thus IEEE-754 is quite valid reference. It show basic you have to consider in order to avoid problems as reported.

I have had found more unexpected results, but I do not have any more time to spend on this, especially if you are not ready to do anything about and refuse any valid suggestions, even from someone made fully functional 64-bit floating point library on plain 16MHz MCUs from ground recently with efficiency suitable to be used in any time critical application and as well a lite version of CAS in the past (actually, it was called differently ten)...

You have a point, it is easy to talk and fairly easier to deny existence of any issue which require fixing. Perfect program by definition does not exist, why denying obvious? You have a daily job as anyone else, but as well probably responsibility to maintenance CAS for HP.

BTW, If I ever manage to find the backup CD with the old version, I will first send to you to test. It was a toy, yes, made for fun only as a challenge to spare time for mainly symbolic higher order derivation and desired 2D and 3D graph displaying, but what was capable to do was done properly and fast. I have also had much better things to do in multiple fields in past 30+ years, than improving that single project to a powerful CAS...

And the last unexpected result I have found in Prime was:
limit(x/ABS(x),x,0) => 0 ?!? (including limit from left and right)

At end, if you treat all as personal attacks, it is really no point to waste more time on this. It is anyway up to you what to do. If you, HP and customers are happy with current state, there is no point for evidence of any bug existence...

I wish you all the best, whatever you decide.