List Commands Library for 50g

[pier4r]

(09-29-2017 09:39 PM)DavidM Wrote:  Wouldn't it be easier to simply keep the keys and values in their own lists? That way you achieve the above with { key or value list } <target> LCNT/MPOS/etc.



Give it some thought. I think you'll find that keeping the keys and values as separate lists has some nice benefits, and KSORT provides some nice flexibility by allowing you to execute a user-supplied program on the bundled list.

Yes, as I said, I did not play around with KSORT. Having the two list separated is ok and has advantages (I can even input the bundled list and then build somehow the separated lists).

(09-29-2017 11:30 PM)John Keith Wrote:  Not to be disagreeable, but I have to vote for 2a for several reasons:


IMHO, version 2a would result in less stack manipulation than version 2b in most cases.

John

Then I change my vote to 2a too. As wrote, I don't mind much, I thought that 2b was the most stack friendly solution but it happens that I am wrong. Thanks for the explanations.

PS: little request. If you (as 'you all', not John) are going to reply generically to a long post (that is, not to specific paragraphs), could you please shorten the quoted part?