From: Tanner B. [mailto:firstname.lastname@example.org]
Sent: Thursday, May 11, 2006 3:50 PM
To: ruby-talk ML
Subject: Re: final/closed classes in Ruby (was: Sharp knives and glue)
But any solution you can put into place with pure ruby, can
be circumvented just as easily.
True, but if someone goes out of their way to circumvent your protection
mechanisms, the egg is entirely on their face if something goes wrong as
a result. I consider things like private, protected, etc, to be
advisory, not absolute. You break it, you bought it, and all that.
You can circumvent such constructs in other languages as well. Consider
‘#define private public’. >:)
This communication is the property of Qwest and may contain confidential
privileged information. Unauthorized use of this communication is
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and
all copies of the communication and any attachments.