HP Forums
Yet Another 35s Bug - Printable Version

+- HP Forums (https://archived.hpcalc.org/museumforum)
+-- Forum: HP Museum Forums (https://archived.hpcalc.org/museumforum/forum-1.html)
+--- Forum: Old HP Forum Archives (https://archived.hpcalc.org/museumforum/forum-2.html)
+--- Thread: Yet Another 35s Bug (/thread-120991.html)



Yet Another 35s Bug - Katie Wasserman - 08-09-2007

Here's a really obvious one:

1000
STO J
x<>(J)

You'll get an "INVALID (I)" error message!

While:

RCL(J)

Shows the correct error message: "INVALID (J)"




Re: Yet Another 35s Bug - Vincze - 08-09-2007

How do you do x<>(J)? Is it just the X<>Y?


Re: Yet Another 35s Bug - Paul Brogger - 08-09-2007

It's

x<> == yellow-shifted RCL key

followed by

(J) == decimal point key




35S Yet another bug - Ralph - 08-09-2007

It's Latin I think. I is used for J

It's like Visual Basic 6's error message telling me I'm out of ram when in fact I'm trying to save to a floppy and haven't put it in the drive.

More exactly I think they planned on only one indirect pointer and added J later. BTW I'm happy they did.


Re: Yet Another 35s Bug - Gregg Bergman - 08-11-2007

Maybe not so obvious: 
While in a program.

A001 LBL A
A002 1000
A003 STO J
A004 x<>(J)
A005 RTN

Shows the correct error message: "INVALID (J)"




Re: Yet Another 35s Bug - Katie Wasserman - 08-11-2007

This is even more disturbing.


Re: Yet Another 35s Bug - Larry Holmes - 08-12-2007

I wonder if this has to do with the use of J instead of I in engineering parlance, to represent the imaginary part of a complex number? Is it possible that, by using a different paradigm, this could make sense, and not really be an error? I am not sure how to do that just yet; I plan to buy a 35s and go through some of the errors, etc., to examine these kinds of possibilities, but don't have much to say right now, except to mention ideas like this one.