unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: Guile Developers <guile-devel@gnu.org>
Subject: Re: SLIB support
Date: Sat, 15 Sep 2007 18:53:27 -0700	[thread overview]
Message-ID: <87642bjrzc.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87veaf3nq7.fsf@gkar.rotty.yi.org> (Andreas Rottmann's message of "Wed\, 12 Sep 2007 17\:30\:40 +0200")

Andreas Rottmann <a.rottmann@gmx.at> writes:

> I've now prepared a patch (attached) that's hopefully good enough
> for upstream use.

> +(define-module (ice-9 slib)
> +  :export (slib:load slib:load-source defmacro:load
> +	   implementation-vicinity library-vicinity home-vicinity
> +	   scheme-implementation-type scheme-implementation-version
> +	   output-port-width output-port-height array-indexes
> +	   make-random-state
> +	   -1+ <? <=? =? >? >=?
> +	   require slib:error slib:exit slib:warn slib:eval
> +	   defmacro:eval logical:logand logical:logior logical:logxor
> +	   logical:lognot logical:ash logical:logcount logical:integer-length
> +	   logical:bit-extract logical:integer-expt logical:ipow-by-squaring
> +	   slib:eval-load slib:tab slib:form-feed difftime offset-time
> +	   software-type)
> +  :replace (provide provided?)
> +  :no-backtrace)
> +
> +\f
> +(load "@SLIB_LOCATION@/init/guile.init")

In the long run, or perhaps even in the short run if Aubrey Jaffer's
interested in a patch and can make a fairly quick release, I wondered
if we might want to go even further, i.e. change it so that the *only*
thing in ice-9/slib.scm is

  (load-from-path "slib/guile.init")

I suggest this in part because I believe SLIB already has code (which
might or might not need adjustment) to handle defining the module,
making the exports, etc.  It's just conditionalized on the Guile
version.

If I recall correctly, SLIB's module related code is fairly automated
and is actually part of an implementation independent module
framework.  So the definition in ice-9/slib.scm is probably just a
duplication of effort.

Given that, it seemed like it might be better to just work with Aubrey
Jaffer to maintain all of the code in one place.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4


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


      parent reply	other threads:[~2007-09-16  1:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 17:49 SLIB support Andreas Rottmann
2007-09-12 15:29 ` Andreas Rottmann
2007-09-12 15:30 ` Andreas Rottmann
2007-09-13  7:40   ` Ludovic Courtès
2007-09-13 13:14     ` Andreas Rottmann
2007-09-13 14:15       ` Greg Troxel
2007-09-13 14:35         ` Andreas Rottmann
2007-09-13 15:39         ` Rob Browning
2007-09-13 15:56           ` Andreas Rottmann
2007-09-15  9:10             ` Ludovic Courtès
2007-09-15 11:30               ` Greg Troxel
2007-09-15 17:23                 ` Ludovic Courtès
2007-09-16  0:36                   ` Greg Troxel
2007-10-02  3:25                   ` Ludovic Courtès
2007-09-16  1:41               ` Rob Browning
2007-09-16  1:53   ` Rob Browning [this message]

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=87642bjrzc.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=a.rottmann@gmx.at \
    --cc=guile-devel@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).