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:01 -0500 (EST)
• Organization: There Is No Cabal.
• References: <87u2hxct70.fsf@ethereal.dyndns.org> <brucehoult-2403001218020001@bruce.bgh> <slrn8dli23.fmr.neelk@brick.cswv.com>
• Xref: traf.lcs.mit.edu comp.lang.dylan:11717

neelk@brick.cswv.com (Neel Krishnaswami) writes:

> At a guess, the Dylan designers wanted to make the unit of separate
> compilation larger than a single module, so they could more mileage
> out of aggressive program-analysis compiler optimizations. Since

That's exactly the reason.

> I dunno why modules don't nest, though. Maybe there are theoretical

What do you mean by 'nesting'? It is possible to combine several
modules to a single 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

• OT: What's this? (Re: A basic question: defining modules and libraries)
• From: Nolan Darilek <nolan@ethereal.dhis.org>
• Re: A basic question: defining modules and libraries
• From: neelk@brick.cswv.com (Neel Krishnaswami)

• Re: A basic question: defining modules and libraries
• From: brucehoult@pobox.com (Bruce Hoult)

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