Re: Some Dylan improvements

To: Hugh Greene <q@tardis.ed.ac.uk>
Subject: Re: Some Dylan improvements
From: Jason Trenouth <jason@harlequin.co.uk>
Date: Thu, 30 Mar 2000 16:20:08 +0100
Cc: info-dylan@ai.mit.edu
In-Reply-To: <Pine.GSO.3.96.1000330153038.12320C-100000@tardis.tardis.ed.ac.uk>
References: <38E1B578.BC05AD4E@cup.hp.com> <jtJE4.13391$Of2.562674@typhoon.ne.mediaone.net> <Pine.GSO.3.96.1000330153038.12320C-100000@tardis.tardis.ed.ac.uk>
Sender: owner-info-dylan@ai.mit.edu

On Thu, 30 Mar 2000 09:45:06 -0500 (EST), Hugh Greene <q@tardis.ed.ac.uk>
wrote:

> On Thu, 30 Mar 2000, Scott McKay wrote:
> > Eric Gouriou wrote in message <38E1B578.BC05AD4E@cup.hp.com>...
> > >
> > > Hello,
> > >
> > > Following the module/library discussion, I would expose to the
> > >community some ideas I have on how Dylan could be improved. ...
> > >
> > > Proposed changes (more comments below):
> > > ...
> > >B) add a way to specify a module interface beyond mere names
> > 
> > I think this is a good idea ...  Yes, there is the "two hunks of code"
> > problem, but ... if this were an optional part of 'define module', it
> > would be worth trying. 
> 
> Yes, absolutely, this should be optional, just like type declarations,
> sealing etc.  I see no reason why you shouldn't provide type info for some
> exported names and not for others (in which case they'd effectively have
> type <object>), specially in incremental development.

An alternative might be to put the note on the binding definitions:

	define exported generic foo () => ();

This would avoid the redundancy. Modules definitions would then be reduced to
importing.

__Jason

Follow-Ups:

Re: Some Dylan improvements

From: Hugh Greene <q@tardis.ed.ac.uk>

References:

Some Dylan improvements

From: Eric Gouriou <eric_gouriou@cup.hp.com>

Re: Some Dylan improvements

From: Hugh Greene <q@tardis.ed.ac.uk>