Talk:Thunk (functional programming)

Don't get it
A template from April 2011 complaints that the article is too complicated to understand to a non-technical audience. I simply don't get why it should be comprehensible to a non-technical audience, and why it even could be interesting to a non-technical audience. To explain it to non-technicians,
 * In your programs, that you work with, there are so called "procedures" that perform schematic tasks,
 * these procedures communicate with each other through so called "parameters" that represent some values that procedures communicate with each other
 * (now half of the audience is asleep)
 * but there are various method with which that the procedures update those parameters
 * (the audience is asleep is snoring loudly, the rest is either yawning wildly, or picking their belongings to leave)
 * the procedures, now can be designed to either work with a pointer to the refered values or perusing copies... bla, bla, bla, bla-bla ...
 * (everybody not asleep have since long left the local)

So why should parameter value propagation ever be explained to a non-technician?? Rursus dixit. ( m bork3 !) 19:25, 2 November 2011 (UTC)