+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: HP Prime (/forum-5.html)
+--- Thread: Why are certain commands not documented? (/thread-8584.html)
Why are certain commands not documented? - webmasterpdx - 06-28-2017 02:56 AM
e.g. I've been playing around with the =< operator, which gets translated to array_sto()
....neither of which is in the standard documentation or in the catalog. The only place I can find these is here:
https://tiplanet.org/hpwiki/index.php?title=HP_Prime/Commands
....but these operations are not explained....
Is there any official HP documentation that has this stuff properly documented?
Thx
RE: Why are certain commands not documented? - Anders - 06-28-2017 03:30 AM
Unfortunately, this has been an ongoing topic for a long time. HP Prime is a great platform that is not documented properly (Reference manual or AUG type). People (including me) raised the weak documentation issue more that a year ago and still nothing. The best most current official documentation is the Help button on the calculator. The user guide .pdf file is hopelessly behind.
We are still hoping this will change because HP Prime has great potential.
RE: Why are certain commands not documented? - webmasterpdx - 06-28-2017 03:48 AM
but these cmds aren't even in the catalog, so the help menu won't work on them.....
They allow you to access a matrix/vector by reference.
e.g.
m:=[1 2 3];
l:=m;
m[1]=<4; // gets translated to array_sto(4,at(m,0));
m returns [4 2 3]
l returns [4 2 3] also
So, I know how it works, kinda, but I'd love to find what else is possible (and undocumented).
RE: Why are certain commands not documented? - DrD - 06-28-2017 10:34 AM
This has been discussed here (and elsewhere):
http://www.hpmuseum.org/forum/thread-4127.html?highlight=command+list
RE: Why are certain commands not documented? - Tim Wessman - 06-28-2017 02:51 PM
In this case it was a "feature" that nobody on the HP side was even aware of...
There is also the issue that there are things in the CAS that directly conflict with other things in the core calculator side and we don't particularly want people using because they are problematic in one way or another. Documenting and highlighting them just exacerbates the problem in those cases.
RE: Why are certain commands not documented? - DrD - 06-28-2017 06:40 PM
Tim makes a good point, from a corporate point of view. For fringe users, using the entire field of available resources within the calculator, just adds to the sport. Sort of a twist on the theme, "caveat emptor."
-Dale-
RE: Why are certain commands not documented? - webmasterpdx - 06-29-2017 12:05 PM
being able to access by reference is something that is VERY useful from a programatical standpoint. It could increase speed dramatically for certain applications.
RE: Why are certain commands not documented? - toml_12953 - 06-29-2017 03:19 PM
(06-29-2017 12:05 PM)webmasterpdx Wrote: being able to access by reference is something that is VERY useful from a programatical standpoint. It could increase speed dramatically for certain applications.
It also saves memory when passing large arrays. Instead of having to make a copy of the array, only a pointer to the original array's location is passed.
RE: Why are certain commands not documented? - webmasterpdx - 06-29-2017 08:29 PM
Precisely!