newRPL - build 1255 released! [updated to 1299]
|
06-07-2019, 04:57 PM
Post: #492
|
|||
|
|||
RE: newRPL - build 1255 released! [official and unofficial]
(06-07-2019 02:45 PM)Gilles Wrote:(06-04-2019 08:46 PM)Claudio L. Wrote: I like it as an alternative format for FOR. NEXT would simply advance in the list. Is there any use for STEP? Perhaps add the number to the index within the list, so you can skip backwards or more than one item forward. The loop ends whenever the index is out of bounds. Nice idea, unfortunately it's not doable. When FOREACH is executed, the quantity that STEP will receive on the stack is not known yet (and may vary throughout the loop) so how many elements do we assign on the first run? Also, creating intermediate lists is expensive. The loop would save the list and index on a local unnamed variable, so we can just give it a name (@LIST, @INDEX perhaps?) that the user can use within the loop. We can assign the given variable the current single element, but the user can get any other elements from the list with GET as needed. Another option would be a command that gives you the next or previous element but it's more limited. STEP would just add to the index. Anoooother option is for FOREACH to accept a list of variables instead of a single one: Code: { a b c d e f } FOREACH { I J } ... NEXT STEP would skip the given elements (1 STEP would make the next run be I==b J==c) and could even accept negative values. Loop would end when there's not enough values left on the list to fill all variables.[/code] |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)