HP 50G help

[Han]

(04-24-2015 05:19 PM)Tugdual Wrote:  

(04-24-2015 04:23 PM)DavidM Wrote:  From the AUG (Advanced Users Guide) for the RCL command:

Though it's not stated explicitly, this same behavior is applied to many built-in operations where an implicit RCL of a variable is executed. I can't remember the details at the moment, but I'm pretty sure there are at least a couple exceptions to this rule. It all boils down to which SysRPL opcode is used to get a variable's contents onto the stack. Most of the time the parent directories are searched.

Note that this isn't the same as searching all directories. Just the ones in the current path are included.

It is indeed something fundamental to understand.
But this being said is that the right way to go? The calculator would naturally feed the root directory with a lot of crap and a purge is tedious; my conception of a directory is precisely to isolate/encapsulate problems in their own context. So when I create a subdir I would expect to start with a blank page.
In my humble opinion, this mechanism totally ruin the concept of directories.

I personally think it is the right way to go. If you want to recall or store a value using only the current directory, there is a mechanism to do that:

PATH 'MYVAR' + RCL (or replace RCL with STO)

is the strict way to recall or store values in the current directory. The current mechanism allows one to have a single instance of a variable (in a containing directory) and have it be accessible in all lower subdirectories. Otherwise, we would have a lot of unnecessary redundancy.