List Commands Library for 50g

[DavidM]

(10-05-2017 11:31 PM)Brad Barton Wrote:  How about both?

(10-06-2017 05:58 AM)pier4r Wrote:  If it is not difficult, I would support this.

Thanks for joining in, Brad! I'm glad you're participating, and look forward to your insights. Pier, I'd only be surprised if you didn't support Brad's suggestion.

I'm really more interested in which situation people see as the most common scenario: a "groups" focus, or an "elements" focus. John's example shows how easy it is to switch between the two.

At present, I'm of the opinion that the library already has more commands than can be easily remembered. No matter how good the documentation is, commands aren't much use if you can't remember or find them. I've already seen evidence that existing commands simply aren't being used in situations where they apply, and I believe the size of current command set is contributing to that (especially if you also include GoferLists in the mix). While I'm not absolutely opposed to adding any last minute commands, they really need to be very compelling to overcome my desire to stabilize the library for a "general release".

(10-06-2017 03:23 PM)John Keith Wrote:  I don't see how the connection between LCLLT and LDIST is dependent on whether sublist count or sublist size is used, but I do think it is important that LDIST and LSDIV work the same way.

I was originally thinking that LCLLT would have to change if LDIST did, but that's not the case. Thanks for making me take a second look!

Case in point. Changing only LDIST, the following holds in both scenarios:

{ 1 2 3 4 5 6 } 2 LDIST => { { 1 3 5 } { 2 4 6 } } LCLLT => { 1 2 3 4 5 6 }
{ 1 2 3 4 5 6 } 2 LDIST' => { { 1 4 } { 2 5 } { 3 6 } } LCLLT => { 1 2 3 4 5 6 }

(10-06-2017 03:23 PM)John Keith Wrote:  On the other hand, thinking about these commands made me wonder if it would be useful to have another command which would redistribute the sublists, e. g. converting {{ 1 2} { 3 4 } { 5 6 } { 7 8 } } into { { 1 2 3 4 } { 5 6 7 8 } } or vice versa. Of course this could also be done with user code but it would be substantially longer and slower than a built-in command.

This can be achieved with:

Code:

\<<
  DUP SIZE
  SWAP LXIL
  DUP SIZE
  ROT / LSDIV
\>>

Yes, I know it's more than a few commands, but not by much. And I'm still planning to do some more tweaking of LXIL and LSDIV for speed (once I know the direction to take on the latter).

Perhaps this could show up as a command in some later release after the general one? That's worth considering.