Generaly looks OK.  However, in axFormatOp (in ax.boot) original
version treated both branches of 'If' in symmetric way.  Your
new version is asymmetric.  Why?

Because it is assymetric! In

if X has T then A else B

the B branch would not have to augment X with type T.
Note that I collect all the T that appear in a "has" construction.

It was not a problem in the original $pretendFlag-Version, because there, the T would have been ignored for both branches.

A problem would be something of the form

  if not(X has T) then A else B

but the has construction is very special anyway. Maybe any logical connectives that involve "X has T" inside a "if" condition should be forbidden.

For example, one cannot sensibly augment the type of X inside A in a construction like

  if X has T or prime? p then A else B

(Well, "and" could be allowed and transformed into multiple if's.)

I'm going to work on more documentation tonight. And also on the issue that Bill reported.

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.

Reply via email to