unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: find-versioned-module bugs
Date: Wed, 16 Jun 2010 01:12:06 +0200	[thread overview]
Message-ID: <874oh3hovt.fsf@gnu.org> (raw)
In-Reply-To: m3bpbjndsl.fsf@pobox.com

Hello,

Andy Wingo <wingo@pobox.com> writes:

> While this was a noble sentiment, and a consistent strategy, it's not
> the right thing IMO. Versions were not a well-considered addition to the
> spec, and we should not feel compelled to (a) promote them, or (b) to
> implement them ideally (according to their ideals).

+1

In particular we could choose to ignore version specs altogether.

(Ironically, given the tendency of WG1/2 to ignore R6RS, along with
implementors stating they implement “languages descending from Scheme”
as opposed to just “Scheme” [0], it may well be that ‘6’ will be the
only version number ever used.)

> In our case, my opinion is that we should change the rule to be, "the
> first compatible version found in the path"; though perhaps we should
> wait for confirmation from Ludovic.

I’m a bit lost.  As you said on IRC, we should probably start by looking
at what other implementations do (for those implementations that resolve
modules at run-time, that is.)

Thanks,
Ludo’.

[0] http://www.racket-lang.org/new-name.html




  parent reply	other threads:[~2010-06-15 23:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  7:11 find-versioned-module bugs Andy Wingo
2010-06-09 12:40 ` Julian Graham
2010-06-10  4:25   ` Julian Graham
2010-06-10 12:23     ` Andy Wingo
2010-06-10 14:02       ` Julian Graham
2010-06-10 14:49         ` Andy Wingo
2010-06-14 22:53           ` Andy Wingo
2010-06-15  5:02             ` Julian Graham
2010-06-15  7:34               ` Andy Wingo
2010-06-17 12:58                 ` Julian Graham
2010-06-18  8:28                   ` Andy Wingo
2010-06-15 23:12           ` Ludovic Courtès [this message]
2010-06-16  7:23             ` Andy Wingo

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=874oh3hovt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.org \
    /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).