OK, I see mode_declare is used to declare variables and functions. I had not made sense of it before - I had thought it was for functions and arguments. I could use it to get rid of the warnings and presumably speed the program up it it is compiled. Does it do anything if the program is interpreted? It did not seem to, as I had invalid ones and got no error. Are the variables local? I can figure this out by experimenting, but that seems unnecessary. But I could not then use big floats, which I am not now, but would like to. I could try to make it work both ways - that is one could choose either. I hope I am not asking too much, but some of this I wish I had asked earlier.
Dennis J. Darland
dennis.darland at yahoo.com
http://dennisdarland.com/http://dennisdarland.com/dennisdaze/http://dennisdarland.com/philosophy/http://sode.sourceforge.net/
"According to the World Health Organization, the warming of the planet caused an additional 140,000 deaths in 2004, as compared with the number of deaths there would have been had average global temperatures remained as they were during the period 1961 to 1990. This means that climate change is already causing, every week, as many deaths as occurred in the terrorist attacks on September 11, 2001"
-- Peter Singer _Practical Ethics, Third Edition_, p. 216.
--- On Thu, 8/9/12, Dennis Darland <dennis.darland at yahoo.com> wrote:
> From: Dennis Darland <dennis.darland at yahoo.com>
> Subject: Warnings compiling
> To: maxima at math.utexas.edu, "Robert Dodier" <robert.dodier at gmail.com>
> Date: Thursday, August 9, 2012, 7:40 PM
> Compiling I get many warnings about
> undefined variables. As I understand it 'define variable'
> defines global variables. Many of the variables I got
> warnings for I would not want to be global. Is there a way
> to define local variables? Others are arrays. The arrays
> worked as global OK when the code was being interpreted. I
> could not figure how to define arrays in define_variable
> either. That was some time ago. Also, the code ran even with
> the warnings, but was no faster. Also variables defined with
> 'define variable, were also listed. Perhaps because this was
> called in the main function, and the variables appeared in
> functions before it in the file.
>
> Dennis J. Darland
> dennis.darland at yahoo.com
> http://dennisdarland.com/
> http://dennisdarland.com/dennisdaze/
> http://dennisdarland.com/philosophy/
> http://sode.sourceforge.net/
> "According to the World Health Organization, the warming of
> the planet caused an additional 140,000 deaths in 2004, as
> compared with the number of deaths there would have been had
> average global temperatures remained as they were during the
> period 1961 to 1990. This means that climate change is
> already causing, every week, as many deaths as occurred in
> the terrorist attacks on September 11, 2001"
> -- Peter Singer _Practical Ethics, Third Edition_, p. 216.
>
>
> --- On Thu, 8/9/12, Robert Dodier <robert.dodier at gmail.com>
> wrote:
>
> > From: Robert Dodier <robert.dodier at gmail.com>
> > Subject: Re: [Maxima] Timing comparison for diffeq
> program in c++, Maple and Maxima
> > To: maxima at math.utexas.edu
> > Date: Thursday, August 9, 2012, 6:54 PM
> > On 2012-08-09, Dennis Darland <dennis.darland at yahoo.com>
> > wrote:
> >
> > > I had a lot of trouble with arrays in maxima.
> >
> > Yeah, arrays are difficult to work with. There are
> probably
> > some
> > relatively simple things that could be changed to make
> it
> > easier,
> > although nothing on the horizon yet.
> >
> > best,
> >
> > Robert Dodier
> >
> > _______________________________________________
> > Maxima mailing list
> > Maxima at math.utexas.edu
> > http://www.math.utexas.edu/mailman/listinfo/maxima
> >
> _______________________________________________
> Maxima mailing list
> Maxima at math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima
>