git://www.ginac.de
/
ginac.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
29b4207
)
Removed remark that symbols always commute.
author
Chris Dams
<Chris.Dams@mi.infn.it>
Thu, 23 Feb 2006 14:39:42 +0000
(14:39 +0000)
committer
Chris Dams
<Chris.Dams@mi.infn.it>
Thu, 23 Feb 2006 14:39:42 +0000
(14:39 +0000)
doc/tutorial/ginac.texi
patch
|
blob
|
history
diff --git
a/doc/tutorial/ginac.texi
b/doc/tutorial/ginac.texi
index ad48666c783e916c607579191c221c5d2b2fcb13..92d8fca38933bdfd9ff8d307849ead1139a071bc 100644
(file)
--- a/
doc/tutorial/ginac.texi
+++ b/
doc/tutorial/ginac.texi
@@
-3011,10
+3011,8
@@
expressions. Also, non-commutative products in GiNaC are more intelligent
than in other computer algebra systems; they can, for example, automatically
canonicalize themselves according to rules specified in the implementation
of the non-commutative classes. The drawback is that to work with other than
than in other computer algebra systems; they can, for example, automatically
canonicalize themselves according to rules specified in the implementation
of the non-commutative classes. The drawback is that to work with other than
-the built-in algebras you have to implement new classes yourself. Symbols
-always commutate and it's not possible to construct non-commutative products
-using symbols to represent the algebra elements or generators. User-defined
-functions can, however, be specified as being non-commutative.
+the built-in algebras you have to implement new classes yourself. Both
+symbols and user-defined functions can be specified as being non-commutative.
@cindex @code{return_type()}
@cindex @code{return_type_tinfo()}
@cindex @code{return_type()}
@cindex @code{return_type_tinfo()}