Re^4: naming anonymous subroutines inner variables

Be careful!

Wise words. When I first posted this, I thought about adding some sort of note of caution about the aliasing, or just avoiding it altogether in the pseudo-code, but desisted because of concerns about minimizing changes to the OPed code and about brevity. The approaches here and here that entirely avoid aliasing are much better: an aliasing bug, if it manifests, can be a really nasty critter to deal with!

Give a man a fish: <%-{-{-{-<

Comment on Re^4: naming anonymous subroutines inner variables Download Code

Replies are listed 'Best First'.
Re^5: naming anonymous subroutines inner variables by BrowserUk (Patriarch) on Jun 22, 2016 at 23:55 UTC
an aliasing bug, if it manifests, can be a really nasty critter to deal with! Indeed. I remember vividly several days and nights trying to track one such down whilst under pressure to complete. Not nice. The other side is that used with knowledge, caution and clear commentary warning, it can be an extremely powerful technique. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice. Not understood.	[reply]
Re^6: naming anonymous subroutines inner variables by AnomalousMonk (Archbishop) on Jun 23, 2016 at 00:00 UTC
... used with knowledge ..., it can be an extremely powerful technique. With great power comes great responsibility — and perhaps a few sleepless nights! Give a man a fish: `<%-{-{-{-<`	[reply] [d/l]


Syntactic Confectionery Delight
	PerlMonks