Re: Landscape DM42?
Posted: Sat Apr 13, 2019 6:53 am
Sounds like SST....
Yeah, but what, oh great master, shall SST^ and SST-> do?? Noone explained so far. There must be great benefits rewarding the dedication of a primary function, I assume. Oh master, please enlighten us mere mortals.Thomas Okken wrote: ↑Sat Apr 13, 2019 4:36 amUmmm, maybe you might want to kindly take a look at that picture in my post, which, in your rush to point out the dumbest possible interpretation of what I wrote, you apparently didn't have time to inspect...
I agree Walter, no need to be nasty. It was possible (easy?) to read your note to mean it was implied he didn't know the count; sure, that's not what you meant, I knew that, but it it could have been taken that way, and if meant so, would be insulting...
Thanks, Bob, for a reasonable explanation. There is, however, also SST without any arrow on said keyboard layout. So we can see three SST's there, can't we?rprosperi wrote: ↑Sat Apr 13, 2019 3:04 pmThese have been discussed a lot lately (though mostly at MoHPC) as new features (the 2nd is new, the first had a minor name change to clarify the difference) for Free42, and they are Step-Into and Step-Over respectively. Step into is the classic SST that will traverse down into a subroutine, Step-Over will execute the full subroutine and then stop on the next statement after (thus presuming you don't want to explore/debug within the subroutine)
The original discussion is here: https://www.hpmuseum.org/forum/thread-1 ... #pid114162Walter wrote: ↑Sun Apr 14, 2019 12:31 amThanks, Bob, for a reasonable explanation. There is, however, also SST without any arrow on said keyboard layout. So we can see three SST's there, can't we?
(BTW, if a specific topic is discussed elsewhere comprehensively, a link to that location should be easy to place, shouldn't it? By the author of the OP, of course. Not everyone reads everything everywhere always. Just my 20 m€.)
Ay, there's the rub! When you are debugging, you tend to use SST a lot, and having it be shifted becomes very annoying, which is why I felt it would be a good idea to dedicate a key to it (and to SST→ in particular). Personally, I use it a lot more than, say, Σ+.
Thanks again, Bob, that helped. To spare other readers a search through the internet, I publish here where I finally found what I was looking for: https://thomasokken.com/free42/history.html and searching for SST. It reads:rprosperi wrote: ↑Sun Apr 14, 2019 6:01 amThe original discussion is here: https://www.hpmuseum.org/forum/thread-1 ... #pid114162
The 3 SST variations seen in Thomas' screen shot probably correlate with the types discussed in the thread, but I'm not sure which is which as the exact labels differ. No matter though as the point is the same, that extra keys in a layout could be well utilized to provide easy access to some of the SST commands. IMHO, debugging is not done often enough (compared to actual use) to justify such high priority real estate as a primary key, though when you are debugging they sure are handy and at that moment in time, seem well-justified (which has led in the past to discussions of adding a temporary debug mode which would promote some keys to act as SST, etc. while in that mode, but that is a different topic).
hth
(Additional structure and insert in double parentheses by me. Although why couldn't the OP publish that link? Or explain his labels himself? Riddles over riddles... Oh, the world is imperfect.)2019-03-26: release 2.1
- New functions: SST↑ (Step Out) and SST→ (Step Over).
Step Out runs the program until the end of the current subroutine;
Step Over executes one step, but if that step is an XEQ, SOLVE, or INTEG, it runs until the subroutine returns, or SOLVE or INTEG are done.
When Step Out is performed in a function called by SOLVE or INTEG, the program runs until SOLVE or INTEG are done.- Added SST↓ (Step Into), which is just an alias for ((traditional)) SST. This allows creating a row in the CUSTOM menu with SST↓, SST→, and SST↑, like in typical high-level language debuggers.