ΥΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΈ ³ HP48 G/GX Bug ³ ΥΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΟΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΟΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΈ ³ :portnum: { dir ... var } RCL/EVAL fails if portnum >= 2 ³ ΤΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΎ by Joe Horn Another G/GX bug has been identified. Thanx to Jeff Healey and Mohamed Fatri for narrowing the search for me. Here's the scoop. Suppose you have a directory called AAA which contains a subdirectory called BBB which in turn contains a variable called CCC. If you store AAA in a port, you are supposed to be able to recall CCC to the stack by executing :portnumber: { AAA BBB CCC } RCL THIS WORKS FINE on the HP48 S, SX, and G. But it FAILS on the GX if the portnumber is 2 or higher. In that case, the GX says "RCL Error: Undefined Name". Ditto for EVAL in place of RCL. Ditto if the wildcard portnumber :&: is used, and the object exists only in port(s) >= 2. Note: This bug only occurs if the list contains more than one name. A portnumber-tagged list containing only one name is identical in operation to a portnumber-tagged name, and works fine in all HP48 models & versions. This bug may be removed in a future version of the GX. Check your GX to see if it has this bug.