X-From-Usenet: see Received: header above.
X-rubymirror: yes
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at
ruby-lang.org
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Precedence: bulk
Lines: 25
List-Id: ruby-talk.ruby-lang.org
List-Software: fml [fml 4.0.3 release (20011202/4.0.3)]
List-Post: <mailto:ruby-talk ruby-lang.org>
List-Owner: <mailto:ruby-talk-adminruby-lang.org>
List-Help: <mailto:ruby-talk-ctlruby-lang.org?body=help>
List-Unsubscribe: <mailto:ruby-talk-ctlruby-lang.org?body=unsubscribe>
X-Virus-Scanned: amavisd-new at yahoo.com
Tomasz Wegrzanowski wrote:
> Ruby object model is almost like Smalltalk's. There are
objects that
> receive messages and everything is context-independent.
The main
> difference is that they have two interfaces, not one.
They have an
> interface for generic messages (like Smalltalk
objects), and a special
> interface for "implicit self" messages. (from
the inside the
> difference is much bigger, but that's not important
here)
I actually see the presence of these two interfaces
beneficial.
Using aux methods which are not intended to be part of the
public
interface is unevitable programming practice. The need to
take it out
from the public interface is also a very basic request.
This should be solved in the core language (as others said
before,
no dozen witty hacky metaprogramming snippets for this,
please).
If not in the way it is done now, how would you do it?
(Well, at least it's clear how not to do it. I think of
Python's horrid
name
manglng...)
Csaba
|