DB48X: HP48-like RPL implementation for DM42

[grbrum]

Hello, thank you for the trust

To spare you the full read, I changed the state to DEMO and the problem does not occur anymore, sorry about the inconvenience.
my test state only has a couple of programs and the following lines in the end:

NoTrailingDecimal
4 Fix
4 DisplayDigits
Dec
NumberDotOrComma
8 WordSize
HomeDirectory

I deleted everything above HomeDirectory and the problem is solved. all is good now
since I tried this last, I had already written the comments below.

Quote:The bad news (for me) is that I trust you, so I suspect a display problem. We can check that quickly by calling LOG on the result you see, and checking if you get something closer to 2.7 or to 6.7. If you get 6.7, then it means the result was actually wrong. If you get 2.7, it means that the result was correct but displayed incorrectly.

I get 2.7

Quote:Based on you typing 5,000,000, I suspect that you are using different settings for display, which might explain why I don't see it

I actually get 5000000. then I put 5 million on the stack, I get the following:
2| 5000000
1| 5,000,000
if I do LOG on 5,000,000 I get 6.7, if I do LOG on 5000000 I get 2.7.

Quote:How the heck did you get a Z release? Did you build it yourself? Or did I actually publish a Z release by mistake?

[/php]
I checked again, in VERSION, this is the version number 0.8.0Z - running on DM42.

I downloaded it yesterday in the afternoon (~12:30 PM Central USA) - db48x-v0.8.0.tgz - I can share with you the binary, via email is better?

Quote:I just downloaded the file from GitHub and reinstalled, just to make sure, and my DM32 shows v0.8.0. If GitHub shared a v0.8.0Z with you, then I'd really like to understand why. This might suggest that updating a release binary on GitHub to fix a mistake is not instantaneous, or simply that you were unlucky enough to download a transitory 0.8.0Z before I saw my mistake and replaced it with the correct 0.8.0.

That being said, I seriously doubt "my" 0.8.0Z would be the source of your problem, as it was just a couple of lines changed in the release note.

I tried reinstalling the binary I downloaded yesterday and version 0.8.0Z is still loaded, and indeed downloading it again I now get version 0.8.0.
And you are right, the new version 0.8.0 still presents the problem.