Very interesting.
So, taking away from this....
construct a mapcar statement logically based on which functions needed to operate on which list, but all elements of that list.
Function can be a primitive such as '+ '- '* '/ a subfunction defined elsewhere or an anonymous function calling lambda (typically when the only call to that function is within the mapcar statement itself).
Lambda accomplishes any task in a very similar manner as (defun) except it's usually a helper function, being as such it does not have it's own command to call nor does it require any additional memory usage once the task has been completed.
Lambda will be used typically when a list or an item must be processed in an unstandard manner, when there is no autolisp function or call that would in one step accomplish the same task.
Examples are given above, well, one in specific but it bears repeating just for clarity's sake....
For instance, adding 12 inches elevation to a set of points. There's no autocad function or command that operates on the z coordinates only of points, unless we're in the properties window. Well, that's why a lambda was used.
So both of these functions are used in necessity, typically only when the conditions for firing them off aren't met elsewhere. Mapcar expects a function and a list every time, and as such hopefully some others without a full understanding are starting to gain one- powerful stuff , here. Lists are one of the most extensively used data types that I see from day to day and it's no surprise that a programmer would want to construct a list and then perform operations on it. Something as simple as
(setq nameslist (list "Brandon" "carrie" "john" "frank" "tod" "bill"
"Shannon"))
("Brandon" "carrie" "john" "frank" "tod" "bill" "Shannon")
Command: (mapcar
(_> 'strcase
(_> nameslist
(_> )
("BRANDON" "CARRIE" "JOHN" "FRANK" "TOD" "BILL" "SHANNON")
Is an effective way to showcase the more basic capabilities of mapcar, although indeed on a very rudimentary level.
This function, along with all of your posts and assistance (and fixos curveball, totally worth the discussion) have really made mapcar appear as a tame animal, not so difficult once your head is wrapped around the basics...... the real wild thing is lambda, and i'm fine with that. Constructing on-the-fly functions that have no real use outside of the defun itself are pretty advanced programming, imo, and I look forward to a day where I can use them as fluently as pbejse and/or leemac. No offense others but I frequently see these two using and abusing lambda to spread joy to nerds in need everywhere.
I won't press too hard right now to fully understand the most apt uses of lambda but even a few easier functions that at least allow some comprehension and when/where a lambda might be useful seem the most correct steps to take at the moment, much in the same way that mapcar was approached in this thread.
Another time, as client work beckons
Fixo, Lee, Rhino, mailmaverick, Gile, jvillareal---much obliged. This was a big step.