Re: [Maxima-discuss] How to make buildq evaluate its first argument - please help

[Stavros M. <mac...@al...>]

Well, let's list the ways they get into trouble and see what we can do
about them.

Here are some off the top of my head:

* not all of Maxima allows x[1] where it allows a variable
** for x[1] thru 3 => syntax error
** function, block, and lambda formals (do we really want x[i] and x[2] as
formals?)
** ... I'm sure there are more

* the relationship between x[i] and i, x[1] and x[i], or x[i] and x[j]
** diff(x[i],x[j]) => 0 instead of kron_delta(i,j)
** diff(x[y],y) =>0 ... should be a noun-form (or an error)
** diff(sum(x[i],i,0,n),x[j]) => 0 ... should be (if j>=0 and j<=n then 1
else 0)
** etc.
... these should all be fixable

* you need to be sure to use mapatom instead of atom in many cases

* what else?



On Wed, Apr 23, 2014 at 5:16 PM, Barton Willis <wi...@un...> wrote:

>
>    ​​
> > I
> ​ agree with Robert that we shouldn't be warning users against using
> features we think are working correctly. If we think they aren't working
> correctly,
> > we should fix or remove them.
> And I'm not sure what "uncritical use" is anyway.
>
> Users sometimes use x[1] only because they like the way it prints. Then
> they get into trouble.
>
> --bw
>