- Added a clarification about branch cuts.

[ginac.git] / doc / tutorial / ginac.texi

diff --git a/doc/tutorial/ginac.texi b/doc/tutorial/ginac.texi
index af43c97312320607e6b744463d81c8e680355634..aba77986af2b212ea247f1de5ed022c9bb5a0c20 100644 (file)
--- a/doc/tutorial/ginac.texi
+++ b/doc/tutorial/ginac.texi
@@ -1028,7 +1028,7 @@ for exclusive or.  (It would be embarassing to return @code{1} where one
 has requested @code{2^3}.)
 @end itemize
 
-@cindex @code{ginsh}
+@cindex @command{ginsh}
 All effects are contrary to mathematical notation and differ from the
 way most other CAS handle exponentiation, therefore overloading @code{^}
 is ruled out for GiNaC's C++ part.  The situation is different in
@@ -1105,8 +1105,16 @@ gamma(x+1/2) -> gamma(x+1/2)
 gamma(15/2) -> (135135/128)*Pi^(1/2)
 @end example
 
-Most of these functions can be differentiated, series expanded and so
-on.  Read the next chapter in order to learn more about this.
+@cindex branch cut
+For functions that have a branch cut in the complex plane GiNaC follows
+the conventions for C++ as defined in the ANSI standard.  In particular:
+the natural logarithm (@code{log}) and the square root (@code{sqrt})
+both have their branch cuts running along the negative real axis where
+the points on the axis itself belong to the upper part.
+
+Besides evaluation most of these functions allow differentiation, series
+expansion and so on.  Read the next chapter in order to learn more about
+this.
 
 
 @node Relations, Important Algorithms, Built-in functions, Basic Concepts
@@ -1535,7 +1543,7 @@ authors---they will happily incorporate them into future versions.
 @c    node-name, next, previous, up
 @section What doesn't belong into GiNaC
 
-@cindex @code{ginsh}
+@cindex @command{ginsh}
 First of all, GiNaC's name must be read literally.  It is designed to be
 a library for use within C++.  The tiny @command{ginsh} accompanying
 GiNaC makes this even more clear: it doesn't even attempt to provide a