As you say, have fun - so I won't waste time responding to most of
this, since we've had this discussion before, except to clarify two
things.
> > 1) Killer app in web-based interface
I mean that the web interface IS the killer app.
> > 3) Has access to huge amounts of other libraries
>
> I thi
On Sep 23, 7:43 pm, kcrisman wrote:
> On Sep 23, 11:19 am, rjf wrote:
>
> > On Sep 23, 5:36 am, Burcin Erocal wrote:
>
> > > I think it would be a huge overstatement to say that the symbolics
> > > subsystem in Sage was "designed" in any way. IMHO, it was mostly
> > > patched together to suppo
On Sep 23, 11:19 am, rjf wrote:
> On Sep 23, 5:36 am, Burcin Erocal wrote:
>
> > I think it would be a huge overstatement to say that the symbolics
> > subsystem in Sage was "designed" in any way. IMHO, it was mostly
> > patched together to support educational use, then acquired more cruft
> >
> See #9835 and #9961 on the issue tracker. The patch by Robert
> Marik attached to #9835 solves the problem you show below.
I applied the #9835 patch, no effect, same outcome for the earlier
posted example.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe fr
To implement the proviso system I mentioned would require that
it be deeply embedded in the algorithms. Whenever an algorithm
(say, division) did an operation that involved a proviso it would
need to (a) decorate the result with the proviso and (b) potentially
split the answer into separate sub-a
On Sep 23, 5:36 am, Burcin Erocal wrote:
> I think it would be a huge overstatement to say that the symbolics
> subsystem in Sage was "designed" in any way. IMHO, it was mostly
> patched together to support educational use, then acquired more cruft
> through several rewrite attempts and cramped
The problem is called the "proviso" problem, as in things like
1/x provided x != 0
I did thesis work in this area. One of the attacks is to use
cylindrical algebraic decomposition (CAD). A second approach
is to create a tree of expressions based on intervals such as
[1/x where x < 0] [1/x where
> > So this known problem (at least since 1974) was off the radar of the
> > brainiacs
> > who designed all those subsequent systems, including I suppose, Sage.
>
> I think it would be a huge overstatement to say that the symbolics
> subsystem in Sage was "designed" in any way. IMHO, it was mostly
On Wed, 22 Sep 2010 11:40:44 -0700 (PDT)
rjf wrote:
> Many features in Maxima do not use the "assume" features at all.
> If Macsyma were to be redesigned from the ground up, the issues
> related to assume etc would probably be addressed at a foundational
> level.
>
> To the extent that other com
Many features in Maxima do not use the "assume" features at all.
If Macsyma were to be redesigned from the ground up, the issues
related to assume etc would probably be addressed at a foundational
level.
To the extent that other computer algebra systems claim to be a fresh
look at issues, it appea
10 matches
Mail list logo
