- GiNaC-devel - ginac.de

patch for unarchiving
by Chris Dams 30 Jun '03

30 Jun '03

Hello, I found out that if an add or a mul are unarchived no sorting of terms or factors occurs. Since the canonical ordering depends on the order in which symbols are declared and thus may well be different in the archiving and the unarchiving program, I think this is wrong. A patch is attached that is supposed to solve this. Bye, Chris Dams

2 1

typing error in mul.cpp
by Chris Dams 20 Jun '03

20 Jun '03

Hello nice GiNaC people, Could you please change the line for (its = ls.begin(), itr != lr.begin(); its != ls.end(); ++its, ++itr) that occurs in the file mul.cpp in the function mul::algebraic_subs_mul into for (its = ls.begin(), itr = lr.begin(); its != ls.end(); ++its, ++itr) (i.e., remove an exclamation mark). This should give less segmentation faults in my programs. Bye, Chris Dams

2 3

GiNaC 1.1.1 released
by Christian Bauer 18 Jun '03

18 Jun '03

Hi! With one last-minute bug-fix sneaked in by the ever-helpful Chris Dams, we'd like to present GiNaC 1.1.1 which is crunchy on the outside but soft and delicious on the inside: - lst (and exprseq) provide iterators for read-only element access. For sequential access this is one order faster than using op(). - Implemented relational::subs() (this was done in 1.0.9 but inadvertently omitted from the 1.1 branch). - pole_error and do_taylor are available to library users. - Added on-line help and Tab-completion for print(), iprint(), print_latex() and print_csrc() in ginsh. Get it from your favorite FTP server: ftp://ftpthep.physik.uni-mainz.de/pub/GiNaC There's nobody here to drink champagne with, so I can save to money for buying more C++ books... Happy computing, Christian -- / Physics is an algorithm \/ http://www.uni-mainz.de/~bauec002/

1 0

Bug in diff
by Ola Skavhaug 21 May '03

21 May '03

Hi. I think I've encountered a bug in GiNaC-1.0.13 (on a Debian Linux machine) In ginsh: > diff(sqrt((-sin((x)))^(2.0)),x); (1.0+5.0165576136843360246E-20*I)*sin(x)*cos(x)*((-sin(x))^(2.0))^(-1/2) The answer should be: sin(x)*cos(x)*((-sin(x))^(2.0))^(-1/2) I have not tried to figure out why this happens (perhaps an uninitialized variable?) I've compiled ginac by myself, using cln-1.1.5 (gcc 3.2 compiler) Sincerely, -- Ola Skavhaug, Simulant, stipendiot og enkel gutt fra landet.

2 1

Ginsh: ?? does not list all functions
by Peter Gawthrop 06 May '03

06 May '03

I am using the ginac-tools package in the debian testing distribution. Ginsh does not list print_latex or print_csrc in response to ??. This is important to me as I use this feature to generate wrapper function for use with Octave (www.octave.org) Ginsh gives the following: peterg@tiree:peterg$ ginsh ginsh - GiNaC Interactive Shell (GiNaC V1.1.0) __, _______ Copyright (C) 1999-2003 Johannes Gutenberg University Mainz, (__) * | Germany. This is free software with ABSOLUTELY NO WARRANTY. ._) i N a C | You are welcome to redistribute it under certain conditions. <-------------' For details type `warranty;'. Type ?? for a list of help topics. > ?? Available help topics: Li2, Li3, Order, acos, acosh, asin, asinh, atan, atan2, atanh, beta, binomial, charpoly, coeff, collect, collect_common_factors, collect_distributed, content, cos, cosh, decomp_rational, degree, denom, determinant, diag, diff, divide, eval, evalf, evalm, exp, expand, factorial, find, gcd, has, inverse, is, lcm, lcoeff, ldegree, lgamma, log, lsolve, map, match, nops, normal, numer, numer_denom, op, operators, power, prem, primpart, psi, quo, rem, series, sin, sinh, sprem, sqrfree, sqrt, subs, tan, tanh, tcoeff, tgamma, time, trace, transpose, unassign, unit, zeta To get help for a certain topic, type ?topic > ?print_latex parse error, unexpected T_PRINTLATEX, expecting T_SYMBOL or T_TIME or '?' at print_latex > print_latex((y+z)^(-2)); \frac{1}{{(z+y)}^{2}} > Peter. -------------------------------------------------------------------- | Prof. Peter J Gawthrop | Tel: +44 141 330 4960/2528 | | Centre for Systems and Control & | Fax: +44 141 330 4343 | | Dept. of Mechanical Engineering | Room: James Watt 653 | | University of Glasgow | Email: P.Gawthrop(a)eng.gla.ac.uk | | GLASGOW G12 8QQ, Scotland, UK | URL: www.mech.gla.ac.uk/~peterg | --------------------------------------------------------------------

2 1

patch for function::function
by Chris Dams 30 Apr '03

30 Apr '03

Hello, I found out that if you use the constructor function::function(unsigned ser, const exprseq & es) to construct a function, this function does not get evaluated if the exprseq was already evaluated. The reason is that the expression sequence is copied with the exprseq::copy function and that this takes over the status flags of the already-evaluated exprseq. Therefore I think that the function function::function(unsigned ser, const exprseq & es) : exprseq(es), serial(ser) { tinfo_key = TINFO_function; } that occurs in the script function.pl should be changed into function::function(unsigned ser, const exprseq & es) : exprseq(es), serial(ser) { tinfo_key = TINFO_function; flags = flags & ~status_flags::evaluated; } All the best, Chris Dams

2 1

patch for archiving.
by Chris Dams 30 Apr '03

30 Apr '03

Hello, I found out that during archiving for every expression that is archived all nodes of the archive are searched to see if the expression is already there. This takes way too long for large archives. The solution is to have a map that stores where in the archive expressions are stored. A patch is included. All the best, Chris Dams

2 1

GiNaC 1.2 CVS branch
by Christian Bauer 30 Apr '03

30 Apr '03

Hi! There is now a CVS branch for GiNaC 1.2, intended for all changes that are not binary compatible to 1.1. It can be accessed with the tag "ginac_1-2". Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/

1 0

GiNaC 1.1.0 released
by Christian Bauer 04 Apr '03

04 Apr '03

Lo! Receive now, mylords, version 1.1 of GiNaC, as a gift from one who has nothing, and as a memorial of macros and print_contexts. For now our fate is fulfilled, and-- Oops, I think I got the wrong script here. Anyway... Today, we'd like to present GiNaC 1.1.0. This is the first release since 1.0.0 to introduce incompatible API changes (hence the "1" after the first dot), but unless you are extending GiNaC with your own algebraic classes you probably won't notice (be sure, though, to check the change log for a list of things to watch out for). So rejoice, noble ladies and lords, and behold its mighty features: - Added stream manipulators dflt, latex, python, python_repr, tree, csrc, csrc_float, csrc_double, csrc_cl_N, index_dimensions and no_index_dimensions to control the output format. [That's, like, the coolest thing, if you ask me. Lets you, like, say "cout << latex", and then anything you print will be, like, in LaTeX code. Totally smooth, man...] - subs() accepts an optional "options" argument. The option subs_option::subs_algebraic enables "smart" substitutions in products and powers. [Brought to you by Chris Dams (the real one, not his substitute).] - The scalar_products mechanism allows the specification of an index dimension. [What could be beyond height and width, depth and time?] - Added ex::to_polynomial(). [ex::to_rational()'s evil twin brother.] - Removed deprecated macros is_ex_a, is_ex_exactly_a and friends for good. [Begone, macros! Begone!] - Removed dirac_gamma6/7(). [That's a feature?] - Made the hashing more simple and efficient. [Or so Richy claims...] 'Tis time, methinks, to join the feast: ftp://ftpthep.physik.uni-mainz.de/pub/GiNaC Good night, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/

1 0

GiNaC 1.1 API freeze
by Christian Bauer 19 Mar '03

19 Mar '03

Hi! We plan to release GiNaC 1.1.0 by the end of next week. It will become the new "stable" branch, and any new and exciting experimental stuff will then go into 1.2. Further development of 1.0.x will be limited to bugfixes. The idea is to keep the programming interfaces compatible across all versions of 1.1.x, as it has been the case for 1.0.x, so should there be anyone who has cause why the current 1.1 CVS should not become the 1.1 release version (suggestions for parameter/return type changes, useful additional methods etc.), they must speak now or forever hold their peace. Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/

1 0