From: matz@... (Yukihiro Matsumoto)
Date: 2001-10-05T14:39:04+09:00
Subject: [ruby-talk:22117] Re: Object construction with block and private methods

Hi,

In message "[ruby-talk:22116] Object construction with block and private methods"
    on 01/10/05, Mike Sassak <msassak@speakeasy.org> writes:

|Afterwards, if I run "a.privMethod" I get an error. But not when it's
|initializing. I'm guessing that Ruby allows this because instance_eval
|changes the value of self to be the context of the object. So while it's
|technically not a bug... isn't that still breaking encapsulation?

It is indded.  But instance_eval() is a back door, so it's OK to break
encapsulation.  Encapsulation is not a security scheme, so I believe
it's OK to break when you really want to break.

							matz.