09-09-2019, 05:40 PM

09-09-2019, 10:24 PM

Perhaps some of these implementation limits could be improved/expanded, now that the the Prime G2 with 8 times more Ram is becoming more widely available.

https://www.hpmuseum.org/forum/thread-13621.html

https://www.hpmuseum.org/forum/thread-13621.html

09-10-2019, 01:01 AM

(09-09-2019 10:24 PM)StephenG1CMZ Wrote: [ -> ]Perhaps some of these implementation limits could be improved/expanded, now that the the Prime G2 with 8 times more Ram is becoming more widely available.

https://www.hpmuseum.org/forum/thread-13621.html

Is 3 posts to say the same thing really the way to go here?

I'd say it would be more compelling to explain some sample application or usage where that many vector operations really makes sense being done on a handheld calculator. I'm not saying there aren't any, only that none come to mind, and the work to implement and test that, even if the RAM is available, might better be used for some of the many other places Prime could be improved.

But maybe, with compelling examples, this is could be wrong...

09-10-2019, 04:55 AM

One use for matrices larger than 141*141 would be in investigating image/video processing - but doing that on a PC would be easier. But having lists and vectors have the same size limits would be more robust.

09-10-2019, 11:57 AM

(09-10-2019 04:55 AM)StephenG1CMZ Wrote: [ -> ]One use for matrices larger than 141*141 would be in investigating image/video processing - but doing that on a PC would be easier. But having lists and vectors have the same size limits would be more robust.

Why limit any function or variable artificially? IMHO, it's best to let the machine use all available RAM. On a PC, the only limit to the nesting of subroutines, the size of arrays, etc. is the available RAM, not some arbitrary limit. Let the programmer decide what to use the RAM for!