in reply to Re^3: Catching closures
in thread Catching closures
I guess the OP does not use closures in his code and wants to guard against the unexpected ones.
CountZero
A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James
|
|---|