in reply to Re: Think for yourself.
in thread is the use of map in a void context deprecated ?
Vaguely, because map has control structure characteristics rather than reading purely like a function. Unlike any of the "real" loops it does have a return value, however.
Not so coincidentally, I've sometimes thought it would be nice if for could build a list as well - in which case any distinction between the two would really go out the window for good. Ruby works this way.
Makeshifts last the longest.