You might find this paper (its a PDF) interesting, it is by the same group that brought us Traits. It talks about adding a more flexible encapsulation policy to Smalltalk (it's concepts though are applicable to most dynamic OO languages (perl, python, etc)).
The author discusses the idea that many times you need more than one encapsulation policy. The simplest example being; one for public use, and one for use by subclasses (which would be roughly equivalent to public and protected), but they take it to the next level really. Interesting read.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
