RPL second impressions (HP 28)
|
07-01-2018, 06:39 PM
Post: #37
|
|||
|
|||
RE: RPL second impressions (HP 28)
(06-30-2018 11:35 PM)Valentin Albillo Wrote: So you're advocating sacrificing speed for readability, i.e., completely going against what the RPL paradigm posits. Stack juggling is virtually incompatible with "readability". Most of the "bad" things mentioned here about RPL are a consequence of the particular implementation decisions, rather than the language itself. There's no real reason why using named variables should sacrifice speed, other than that's the way it was implemented, same thing with expressions. As an example, newRPL implements named local variables in a way that using them is as fast (if not faster) than stack juggling. There's also no reason why comments can't be persistent (similar to REM in Basic). I think RPL is not particularly difficult to read, unless you obfuscate the code on purpose for the sake of speed "in-this-particular-implementation". (06-30-2018 11:35 PM)Valentin Albillo Wrote: You know what ? The RPL case reminds me a lot of a hobbyist personal computer of the 80's (I think), the Jupiter Ace, which had a native FORTH implementation out of the box and was being advertised as a fully structured, higher level, much faster language than Sinclair's Spectrum, so supposedly superior and/or more desirable. I loved the Spectrum when growing up, but I quickly abandoned BASIC in favor of raw Z80 assembler, not exactly easy reading material... By the way, DUP SWAP is equivalent to DUP (in your example above). I get that you don't like RPL... cheers! |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)