Re: Q: member syntax in dylan?

• To: info-dylan@ai.mit.edu
• Subject: Re: Q: member syntax in dylan?
• From: Andreas Bogk <andreas@andreas.org>
• Date: Thu, 10 May 2001 11:15:06 -0400 (EDT)
• Organization: TRANSMEDIA GmbH
• References: <200105101013.GAA27213@life.ai.mit.edu> <9de4fr$637a$1@sp15at20.hursley.ibm.com>
• Sender: andreas@teonanacatl.andreas.org
• User-Agent: Gnus/5.0806 (Gnus v5.8.6) XEmacs/21.1 (Capitol Reef)
• Xref: traf.lcs.mit.edu comp.lang.dylan:13288

"Roland Paterson-Jones" <rolandpj@bigfoot.com> writes:

> The motivation is, of course, that it's fun to associate methods with their
> class, particularly when their are no multi-dispatch issues. I believe that
> this encourages object-oriented programming (having come, of course, from
> java and c++).

No, that's just what Java and C++ have taught you, where classes
double as units of encapsulation and units of abstraction. Witness
"friend" classes in C++ to see where this leads to problems.

In Dylan, you group classes and functions that belong together into a
module. This encourages encapsulation, and leaves your choice of class
design alone.

Andreas

-- 
"Der Pirat des Wissens ist ein guter Pirat."

  -- Michel Serres, 
     http://www.heise.de/tp/deutsch/inhalt/co/3602/1.html

• Re: Q: member syntax in dylan?
• From: "Roland Paterson-Jones" <rolandpj@bigfoot.com>

• Prev: Re: Q: member syntax in dylan?
• Next: Redefining CAR/CDR/other standard symbols (was Re: [Q] Dylan to Java/JVM compiler?)
• Index(es):
  • Main
  • Thread