On Mon, Sep 25, 2017 at 3:46 PM, Prof. Dr. Johannes Grabmeier FW <[email protected]> wrote: > I did not meant Segments here, but the reason for using "not" for a unary > function in BitAggregats. > Thanks for your statements, of course one can circumvent all that by > choosing different names, as not, or and and > are reserverd. But why can BitAggregates use these natural names? Of course, > it is clear that _ is the escape sequence, > but it simply does not work for and, or and not, although it does in > BitAggregates. These are the miracles I am after. > > Regards Johannes
I meant that you can use not/and/or as function names (the left side of ==), but your can't use not/and/or as function calls in function definitions (the right side of ==) because they got expand by compiler automatically. So, _and(x, y) == ANOTHER_FUNCTION(x, y) is OK but xor(x, y) == and(x, y) is NOT OK. In BitAggregates, they are parameters to "map", these functions are not called, so that's OK. -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/fricas-devel. For more options, visit https://groups.google.com/d/optout.
