1 | initial version |
This was already reported in Sébastien's answer to:
and made into:
This is already fixed this in Giac; future versions should no longer have this problem.
The place to report Giac issues in general is the Giac/Xcas forum.
2 | No.2 Revision |
This was already reported in Sébastien's answer to:It turns out @Sébastien hit that bug when comparing various integration engines to answer:
and made into:having checked it did not correspond to existing tickets, he opened one for that:
This Bernard Parisse, the main Giac developer, posted there that that problem is already fixed this in Giac; future versions should no longer have this problem.
The place to report Giac issues in general in Giac.
When Sage uses a Giac version with such warnings, silencing them would be nice, see comment 9 by @vdelecroix at Sage Trac ticket 29966. See previous Giac tickets
Regarding where to ask about Giac:
Related:
3 | No.3 Revision |
It turns out @Sébastien hit that bug when comparing various integration engines to answer:
and having .
Having checked it did not correspond to existing tickets, he opened one for that:
Bernard Parisse, the main Giac developer, posted there that that problem is already fixed in Giac.
When Sage uses a Giac version with such warnings, silencing them would be nice,
see comment 9 by @vdelecroix at Sage Trac ticket 29966. See previous Giac tickets29966.
Regarding where to ask about Giac:
Related: