Re: A basic question: defining modules and libraries

• To: info-dylan@ai.mit.edu
• Subject: Re: A basic question: defining modules and libraries
• From: Andreas Bogk <andreas@andreas.org>
• Date: Fri, 24 Mar 2000 11:00:02 -0500 (EST)
• Organization: There Is No Cabal.
• References: <87u2hxct70.fsf@ethereal.dyndns.org> <38DAA0F4.C62AD810@openscript.com>
• Xref: traf.lcs.mit.edu comp.lang.dylan:11718

James <james@openscript.com> writes:

>    I'll try to field this one. Basically, Dylan provides Libraries 
> and Modules as a way of managing namespace. Your code goes inside 

Not only that, but Dylan modules are also the unit of
encapsulation. In C++, the unit of encapsulation is the class. This
gets in your way quite often, and you have to use friend classes or
friend functions.

In Dylan, just put all the classes that have to access each others
internals into the same module.

Andreas

-- 
"Anyone need a DVD decrypter for Linux?
dig @138.195.138.195 goret.org. axfr | grep '^c..\..*A' | sort \
| cut -b5-36 | perl -e 'while(<>){print pack("H32",$_)}' | gzip -d"
  -- James Brister

• Re: A basic question: defining modules and libraries
• From: James <james@openscript.com>

• Prev: Re: A basic question: defining modules and libraries
• Next: Re: Issues with GD
• Index(es):
  • Main
  • Thread