Mac Dude

1182 Reputation

16 Badges

8 years, 119 days

MaplePrimes Activity


These are replies submitted by Mac Dude

@acer: Your interpretation makes sense to me.

Per your last paragraph, I will expect rtables to not get evaluated when passed as a parameter; effectively giving them temporary last-name evaluation type. At the same time, lists will get evaluated fully as the rationale for not doing so isn't present with the immutable structures like lists. This difference in behaviour is good to know and remember. I actually ran against the evaluation of lists already once, when I needed to get at the names of the elements of a list which was passed to a proc; I had to use the ::uneval modifier in the parameter definition of the proc to get at those names. So now I understand why. I do wonder whether all this is unnecessarily complicated, but then, I haven't done enough with Maple yet to make such a statement.

Anyway, I gained some more insight, thanks.

M. D.

Thanks. I hope someone @ Maplesoft sees this & gets it fixed.

 

M.D.

Thanks. I hope someone @ Maplesoft sees this & gets it fixed.

 

M.D.

acer, thanks very much for this clear and comprehensive expose of the diff between list and Vectors, which as I said before I had not appreciated. I certainly did not realize that I cannot really change an element of a list, an operation I need to do often (and am doing on elements of Vectors). Is this what the page you referred me to is calling "being mutable"?

M.D.

acer, thanks very much for this clear and comprehensive expose of the diff between list and Vectors, which as I said before I had not appreciated. I certainly did not realize that I cannot really change an element of a list, an operation I need to do often (and am doing on elements of Vectors). Is this what the page you referred me to is calling "being mutable"?

M.D.

Well, in my version of Maple, 15, firing up the application anew to make sure everything else is flushed out, I get a linear plot. I do not know how to post a plot here so I cannot produce the proof; it is the same curves as in Markiyan's post above; but with a linear vertical scale.

FWIW, here is my .mapleinit file. I do not see how this would prevent logplot in display.

libname:="/Applications/Math_Calc/Maple 15/My_Maple_Libraries",libname:
plots[setoptions](axes=boxed,gridlines=true,symbolsize=20,symbol=solidcircle,font=[Palatino,Roman,14]):
UseHardwareFloats:=true:
Digits:=trunc(evalhf(Digits)):
 print("Maple Init loaded...");

Somehow logplotting is really screwed up in 15; I already had the issue that logplot will ignore, for 15 digits, everything below 10^-7. This one even Maplesoft support verified and acknowledged as a bug (fixed in 16 and not present in 14).

:-(

M.D.

Well, in my version of Maple, 15, firing up the application anew to make sure everything else is flushed out, I get a linear plot. I do not know how to post a plot here so I cannot produce the proof; it is the same curves as in Markiyan's post above; but with a linear vertical scale.

FWIW, here is my .mapleinit file. I do not see how this would prevent logplot in display.

libname:="/Applications/Math_Calc/Maple 15/My_Maple_Libraries",libname:
plots[setoptions](axes=boxed,gridlines=true,symbolsize=20,symbol=solidcircle,font=[Palatino,Roman,14]):
UseHardwareFloats:=true:
Digits:=trunc(evalhf(Digits)):
 print("Maple Init loaded...");

Somehow logplotting is really screwed up in 15; I already had the issue that logplot will ignore, for 15 digits, everything below 10^-7. This one even Maplesoft support verified and acknowledged as a bug (fixed in 16 and not present in 14).

:-(

M.D.

Eric, thanks. I really thought that Vectors were lists... lots to learn I have!

Anyway, good to hear that I am not completely astray with my choice.

...And I already have found today one specific task that I could program using a table rather than a Vector, storing references to Vectors in fact, in a Do loop. Works like a charm.

Thanks,

M.D.

Eric, thanks. I really thought that Vectors were lists... lots to learn I have!

Anyway, good to hear that I am not completely astray with my choice.

...And I already have found today one specific task that I could program using a table rather than a Vector, storing references to Vectors in fact, in a Do loop. Works like a charm.

Thanks,

M.D.

@acer 

Ok, this will get me there. I fiddled around with the Matrix function and its documentation but wasn't able to find this way. Similarly with the angle-bracket notation.

Thanks,

 

M.D.

@acer 

Ok, this will get me there. I fiddled around with the Matrix function and its documentation but wasn't able to find this way. Similarly with the angle-bracket notation.

Thanks,

 

M.D.

Ok, so in this way I can expand the size of M. Is there also a way to append another matrix (which already exists and would have the correct dimensions)?

M.D.

Ok, so in this way I can expand the size of M. Is there also a way to append another matrix (which already exists and would have the correct dimensions)?

M.D.

@acer 

This may do what I want; I'll check it out.

M.D.

@acer 

This may do what I want; I'll check it out.

M.D.

First 35 36 37 38 39 Page 37 of 39