GiNaC-devel

Download

ginac-devel@ginac.de

December 2011

3 participants
2 discussions

[SCM] GiNaC -- a C++ library for symbolic computations branch, master, updated. release_1-4-0-365-ga104ecb
by git＠ginac.de 08 Dec '11

08 Dec '11

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GiNaC -- a C++ library for symbolic computations". The branch, master has been updated via a104ecb34a015fc40a4bdc16ae6ea038ecb8c55d (commit) from dadfd94652601011351c18ae020c5b473fc8e0a3 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit a104ecb34a015fc40a4bdc16ae6ea038ecb8c55d Author: Richard B. Kreckel <rbk(a)bitzer.nodomain.org> Date: Thu Dec 8 16:59:16 2011 +0000 Documentation: Update branch cut convention Now that C++11 is out, there is no more need for oracling about how it might eventually standardize the branch cuts of elementary and inverse trigonometric and hyperbolic functions. ----------------------------------------------------------------------- Summary of changes: doc/tutorial/ginac.texi | 27 +++++++++++++-------------- 1 files changed, 13 insertions(+), 14 deletions(-) hooks/post-receive -- GiNaC -- a C++ library for symbolic computations

1 0

bugs related to parser
by Cedric Studerus 06 Dec '11

06 Dec '11

Dear GiNaC developer, I'm using GiNaC version 1.6.2 with compiler gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2 When working with the parser to read in user defined functions from strings I noticed 3 things: 1) parsing a user defined function (declared to have 1 argument) from a string does not throw an exception when the string contains this function with zero arguments. 2) parsing products of user defined non-commutative functions returns a commutative product 3) The parser accepts userdefined functions with zero arguments and parsing such a function does not throw when there is 1 argument. I have attached a small file "main.cpp" such that you can reproduce this behavior. I'm using these user defined functions with zero arguments but it looks to me like a hack and I would like to know if you are going to allow them ( e.g. with macro definition) or if you completely suppress them in future releases of GiNaC. Thank you very much! Cedric Studerus

2 1