unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: New module system option :duplicates
Date: Tue, 11 Mar 2003 00:38:21 +0100	[thread overview]
Message-ID: <xy765qqu70y.fsf@nada.kth.se> (raw)
In-Reply-To: <878yvrxhp1.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Fri, 07 Mar 2003 10:30:34 -0600")

Rob Browning <rlb@defaultvalue.org> writes:

> Interesting.  Though I had thought that we were already heading in the
> direction of being less tolerant of duplicate bindings as a default.

Yeah.  Default now.

> Also, doesn't ttn already have an augmented module system syntax for
> renaming, etc.?  If so, and if people are using it much, then it might
> be worth considering that syntax as well, and I seem to recall that
> Marius may have been planning something on this front too...

Marius has implemented renaming.  I just augmented it so you can say:

  :use-module ((foo) :prefix foo:)
  
I'll document that in NEWS tomorrow.

>> This implies that x in (math 2D-vectors) can see the methods of x in
>> (my-module) and vice versa, while x in (math 2D-vectors) doesn't see
>> the methods of x in (math 3D-vectors), thus preserving modularity.
>
> Why would x in (math 2D-vectors) be able to see the methods of x in
> (my-module)?  Isn't that a violation of modularity?  The reverse I
> understand.

Think about dynamic method dispatch.  A `paint' method in a generic
graphics package need to see subclasses provided by modules importing
the generic package.

M


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-03-10 23:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 13:19 New module system option :duplicates Mikael Djurfeldt
2003-03-07 14:28 ` tomas
2003-03-07 14:49 ` Marius Vollmer
2003-03-07 15:08   ` Mikael Djurfeldt
2003-03-07 15:28     ` Marius Vollmer
2003-03-07 16:56       ` Rob Browning
2003-03-08 14:38         ` Greg Troxel
2003-03-10 23:39           ` Mikael Djurfeldt
2003-03-11 12:12           ` Mikael Djurfeldt
2003-03-11 12:21             ` Mikael Djurfeldt
2003-03-11 14:29             ` Greg Troxel
2003-03-11 14:47               ` Mikael Djurfeldt
2003-03-10 23:18   ` Mikael Djurfeldt
2003-03-12 15:05     ` Marius Vollmer
2003-03-12 15:18       ` Mikael Djurfeldt
2003-03-12 16:34         ` Marius Vollmer
2003-03-07 16:30 ` Rob Browning
2003-03-10 23:38   ` Mikael Djurfeldt [this message]
2003-03-11  0:14     ` Rob Browning
2003-03-11 10:32       ` Mikael Djurfeldt
2003-03-11 10:50       ` Mikael Djurfeldt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xy765qqu70y.fsf@nada.kth.se \
    --to=djurfeldt@nada.kth.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).