unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: r6rs libraries, round two
Date: Mon, 01 Jun 2009 21:55:32 +0200	[thread overview]
Message-ID: <m3vdnfn2yz.fsf@pobox.com> (raw)
In-Reply-To: <878wkerxar.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Sun, 31 May 2009 00:22:20 +0100")

Hey Julian,

On Sun 31 May 2009 01:22, Neil Jerram <neil@ossau.uklinux.net> writes:

> Julian Graham <joolean@gmail.com> writes:
>
>> 1. Add an optional `version' field to the module record type
>
> Sounds good.

Agreed.

>> * What's a good format here?  We could mirror the requirements of R6RS
>> here (i.e., (v1 v2 ...) where vx is a whole number) or be more
>> flexible.
>
> Given that your objective is to get R6RS library support in, I'd say
> just stick to the R6RS format for now.  It sounds like it will be
> fairly easy to extend this in future, if we want to.

Also agreed.

>> * Should we establish some rules for what you get when you don't
>> specify a version?
>
> Yes!  The latest available?

I don't know. To me this could be a distro decision, like Debian's
"alternatives" system. It would be nice to minimize the number of `stat'
calls it takes to load a library -- which would fall out nicely if when
asking for a module without specifying a version, like `(foo bar)', we
give foo/bar.scm.

In the presence of multiple versions, installation rules could handle
making the symlink so there is a default version -- typically the
version that was installed most recently.

>>  Given what we've decided about loading multiple
>> versions of a library (i.e., you can't)
>
> I didn't follow why we decided that, but it feels wrong to me.  (It
> seems to me that Guile should be able to handle loading ((foo) v1) and
> ((foo) v2) simultaneously as easily as it could handle loading
> ((foo-v1)) and ((foo-v2)) simultaneously.) I guess I should look up
> the previous thread, please let me know if you have a convenient
> reference.

I agree it would be nice, but as I said in the thread that Julian
referenced, that would take some more thought -- more than the R6RS
editors were willing to give the problem. And for us, I suspect we would
need some changes to our hierarchical namespaces. We probably shouldn't
let this be a sticking point for Guile's R6RS libraries support.

Regards,

Andy
-- 
http://wingolog.org/




  parent reply	other threads:[~2009-06-01 19:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 20:31 r6rs libraries, round two Julian Graham
2009-05-30 23:22 ` Neil Jerram
2009-05-30 23:34   ` Julian Graham
2009-06-01 19:55   ` Andy Wingo [this message]
2009-06-01 22:34     ` Ludovic Courtès
2009-06-03 18:36       ` Neil Jerram
2009-06-04  6:50         ` Ludovic Courtès
2009-06-28  0:20       ` Julian Graham
2009-06-28 13:28         ` Neil Jerram
2009-06-28 18:23           ` Julian Graham
2009-06-28 21:40         ` Andy Wingo
2009-06-29 18:01           ` Julian Graham
2009-06-29 18:26             ` Ludovic Courtès
2009-07-06 18:02           ` Julian Graham

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=m3vdnfn2yz.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).