Le dimanche 1 décembre 2019 00:16:24 UTC+1, Thierry (sage-googlesucks@xxx)
a écrit :
>
> Hi,
>
> On Fri, Nov 29, 2019 at 04:41:20PM -0800, rjf wrote:
> > I mentioned in answer to another thread about Maxima/domain/integration
> > the caution that this is likely missing the point.
> >
Hi,
On Fri, Nov 29, 2019 at 04:41:20PM -0800, rjf wrote:
> I mentioned in answer to another thread about Maxima/domain/integration
> the caution that this is likely missing the point.
> Setting a domain or passing this setting to Maxima is not a solution.
> It is likely a symptom that you are
If you have a design for writing the whole thing
from scratch, then that would be worth writing down.
It is not that Sage has to be fixed to call Maxima "the right way".
It is that Macsyma / Maxima does not have a suitable
design. Nor does Mathematica or Maple or (so far
as I can tell) sympy or
On 11/29/19 7:41 PM, rjf wrote:
>
> Perspective: you can diddle with trying to set domains
> "right" but you have probably missed the boat in the
> system design and are unlikely to be able to patch it.
> ...
>
> Sorry for being such a pessimist, but some of us have
> been there.
>
There is
I mentioned in answer to another thread about Maxima/domain/integration
the caution that this is likely missing the point.
Setting a domain or passing this setting to Maxima is not a solution.
It is likely a symptom that you are making a mathematical error.
quoting in part..
Since log() is in
On 11/29/19 2:01 PM, Emmanuel Charpentier wrote:
> Dear list,
>
> We have a non inconsiderable stock of tickets whose analysis ends up
> with someting amounting to "bug due the domain:complex option in
> Maxima", and no solution in view.
Which tickets? Are they all integration?
> Couldn't we
Dear list,
We have a non inconsiderable stock of tickets whose analysis ends up with
someting amounting to "bug due the domain:complex option in Maxima", and no
solution in view.
Couldn't we work around this problem by offering a "domain=" option
(default value =complex") which, when set,
