#3 Tricky use of method slots may backfire

[Tripp Lilley]

"Interesting" uses of a method slot's ability to replace itself with a computed value, or be called as though it were a datum and not code, might backfire if the author doesn't carefully consider what a method slot "means".

The particular example I'm thinking of is Mark-Jason Dominus' "Infinite Lists" in Perl. I could see a situation where someone writes up code that expects to modify its state, but doesn't realize that it will be called every time the slot is accessed in any way...

I might be worrying about nothing, but basically keep your heads up! :)