in reply to Re^3: Closure objects with public, private, and protected fields
in thread Closure objects with public, private, and protected fields

Sure it sucks to have to fix someone else's code because they didn't read the documentation, but it also sucks to be physically restrained from doing something that is perfectly logical simply because the author of an object never conceived that you'd use his object in that particular way.

If you're clever enough to outhink the module author, surely you're clever enough to extend his module to cover your reasonable and well thought out usage pattern?

so in my book flexibility trumps idiot proofing

Flexiblity is comparatively easy; idiot proofing is very, very hard. ;-) Ask anyone who's tried to keep small children (or cats!) safe; it's harder than it sounds sometimes.

--
Ytrew

  • Comment on Re^4: Closure objects with public, private, and protected fields