unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Alex Shinn <alexshinn@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mark H Weaver <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: [PATCH] Add ".guile.sls" and ".sls" to the default %load-extensions
Date: Thu, 8 Nov 2012 11:37:36 +0900	[thread overview]
Message-ID: <CAMMPzYNXRpTE7iP6HchRKC2tdL3C-Lf-v4aB4pvWwknznXTBjw@mail.gmail.com> (raw)
In-Reply-To: <87zk2tkvhx.fsf@gnu.org>

On Thu, Nov 8, 2012 at 5:28 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi!
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> One option would be to return to Aubrey Jaffer's model (used in SCM),
>> where a catalog of modules and their locations is maintained
>
> Hmm, I never really liked that.  And it’s quite an uncommon model.
>
>>> (I’m not sure if searching for a file name with no extension is
>>> intentional.  Ideas?)
>>
>> I looked into this.  Guile has searched for file names with no extension
>> since its initial import into VCS in 1996 (0f2d19dd).  Initially, names
>> with no extension were searched _before_ *.scm, and this logic was
>> hard-coded into the search procedure (try-module-autoload in
>> boot-9.scm).  Jim Blandy introduced the '%load-extensions' variable with
>> default value ("" ".scm") later in 1996 (26544b96), and Mikael Djurfeldt
>> reversed the order to (".scm" "") in 1999 (0a74e31d).  It has been that
>> way ever since.
>
> Woow, thanks for digging it up.  Now we should find out what these guys
> had in mind *before* Guile was first put under version control.  ;-)
>
> Anyway, I still don’t know what to do with .sls.  But the fact that R7
> may come up with its own extension makes me think that maybe we should
> just forget about that extension, as everyone will eventually do.   Hmm?

FYI, there is currently no convention, and the design of
Snow (the library sharing network) does not require any
specific extension (you create and work with packages
which are self-describing via meta-info).

However, for third-party tools it may be convenient to
have a common convention.  Currently Chibi uses .sld
(Scheme Library Definition) to distinguish from R6RS.
These can inline the entire library definition, or use
include files (again, since you specify the filename any
extension will do, and Chibi uses the traditional .scm).

-- 
Alex



  reply	other threads:[~2012-11-08  2:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-04  3:31 [PATCH] Add ".guile.sls" and ".sls" to the default %load-extensions Mark H Weaver
2012-11-04 16:10 ` Noah Lavine
2012-11-04 20:34 ` Ludovic Courtès
2012-11-04 22:27   ` Andreas Rottmann
2012-11-04 23:32     ` Ludovic Courtès
2012-11-05  0:17       ` Andreas Rottmann
2012-11-05 15:16         ` Ludovic Courtès
2012-11-05 20:48           ` Mark H Weaver
2012-11-05 21:15             ` Ludovic Courtès
2012-11-06  2:19               ` nalaginrut
2012-11-06  2:36                 ` Ian Price
2012-11-06  2:56               ` Ian Price
2012-11-06  5:18               ` Mark H Weaver
2012-11-07 20:28                 ` Ludovic Courtès
2012-11-08  2:37                   ` Alex Shinn [this message]
2012-11-08 22:41                   ` Andreas Rottmann

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=CAMMPzYNXRpTE7iP6HchRKC2tdL3C-Lf-v4aB4pvWwknznXTBjw@mail.gmail.com \
    --to=alexshinn@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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).