Re: Short-circuiting a map list.

I propose, until the real map supports short circuiting, instead of mapx or bmap, we call it mapuntil :)

Comment on Re: Short-circuiting a map list.

Replies are listed 'Best First'.
Re^2: Short-circuiting a map list. by davido (Cardinal) on Oct 08, 2011 at 18:50 UTC
I agree; bmap is a bad name. 'break map' is what I saw as its full name when I came up with it. It's not really a 'map until' though. Maybe a map with short circuits, so an 'scmap'. Is that any worse than the very familiar but functionally ambiguous names, "sprintf", "printf", "grep", "chop" and "chomp"? ;) It's unfortunate that there just isn't a nice concise way to clearly summarize every function's purpose with a simple name. If we called it map_with_next_last_and_bail_short_circuits I don't think it would ever gain any measure of acceptance. It may not, even with a concise name, but at least the name wouldn't be the obstacle. Dave	[reply]

Replies are listed 'Best First'.

Re^2: Short-circuiting a map list.
by davido (Cardinal) on Oct 08, 2011 at 18:50 UTC

I agree; bmap is a bad name. 'break map' is what I saw as its full name when I came up with it. It's not really a 'map until' though. Maybe a map with short circuits, so an 'scmap'. Is that any worse than the very familiar but functionally ambiguous names, "sprintf", "printf", "grep", "chop" and "chomp"? ;)

It's unfortunate that there just isn't a nice concise way to clearly summarize every function's purpose with a simple name. If we called it map_with_next_last_and_bail_short_circuits I don't think it would ever gain any measure of acceptance. It may not, even with a concise name, but at least the name wouldn't be the obstacle.

Dave

[reply]