Actually, its not the social problem I am trying to solve. We are a very communicative group and will encourage that to be so with all our new hires. What I am trying to solve is the issue of mis-typing bugs and other insidious things that can happen as a project grows. To be honest, I have been thinking of doing something like this in projects that only I am working on too. Agility is the name of the game these days, and anything that reduces debugging time and therefore increases productivity is a good thing IMO.

I do not believe that the ideas behind encapsulation in languages like C++ and Java are there to solve a social issue. Just as tools like CVS are there not to solve social issues, but instead to better the development process. And all I am trying to do is add another tool to our toolbox to help us to program in a more reliable, bug free way. Its more of a "use warnings" thing, not a "use strict" thing, if you get what i mean.

Also, I like very much what TheDamian said in Re: Re: Re: Tie::SecureHash and AUTOLOAD'ing:

encapsulation is not about preventing access to attributes; it's about controlling access to attributes