I noticed that when using the 'decompiler' see.fs (part of the FF 5.0 distribution) the base is set to hex.
After see is finished the base is not recovered to the base that was in use before see was called/executed.
Please explain why.
see
' cr hex
begin
dup u.4
dup cf@ u.4 u.4
(see) cr
dup 0= \ dup and 0= will be optimised away
until
drop
;
-FredZ
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Why. No special reason, except when I debug and need SEE (and DUMP) I want to work in hex.
And the FF standard prompt always shows you the current base. The scamp does not, so more chance for confusion there.
But you can change it to your liking.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I noticed that when using the 'decompiler' see.fs (part of the FF 5.0 distribution) the base is set to hex.
After see is finished the base is not recovered to the base that was in use before see was called/executed.
see
' cr hex
begin
dup u.4
dup cf@ u.4 u.4
(see) cr
dup 0= \ dup and 0= will be optimised away
until
drop
;
-FredZ
Why. No special reason, except when I debug and need SEE (and DUMP) I want to work in hex.
And the FF standard prompt always shows you the current base. The scamp does not, so more chance for confusion there.
But you can change it to your liking.
Thank you Mikael.
Last edit: Fred Zelders 2025-07-14