From: Eric E Moore <e.e.moore@sheffield.ac.uk>
Subject: Re: :export vs. define-public
Date: Thu, 05 Sep 2002 18:54:53 +0100 [thread overview]
Message-ID: <87fzwo1fv6.fsf@dyn006239.shef.ac.uk> (raw)
In-Reply-To: <87r8g8wd50.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 05 Sep 2002 12:38:03 -0500")
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
Rob Browning <rlb@defaultvalue.org> writes:
> Eric E Moore <e.e.moore@sheffield.ac.uk> writes:
> Actually, I tend to like (export foo) better, but either way I agree,
> :export and (export foo) make it possible to have a common source file
> that you share between different scheme implementations.
I like (export foo) better too. Just the original thread was
:export vs define-public. Since :export and (export) serve similar
purposes, I'd be happy to see one of the two go, but would like to see
at least one kept.
--
Eric E. Moore
[-- Attachment #2: Type: application/pgp-signature, Size: 184 bytes --]
prev parent reply other threads:[~2002-09-05 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 0:41 :export vs. define-public Tom Lord
2002-09-05 0:33 ` Thomas Bushnell, BSG
2002-09-05 0:59 ` cvs access broken? Tom Lord
2002-09-05 18:01 ` Marius Vollmer
2002-09-05 1:02 ` :export vs. define-public Tom Lord
2002-09-05 0:55 ` Thomas Bushnell, BSG
2002-09-05 1:09 ` Tom Lord
2002-09-05 1:12 ` Thomas Bushnell, BSG
2002-09-05 2:05 ` Tom Lord
2002-09-05 16:25 ` Eric E Moore
2002-09-05 17:38 ` Rob Browning
2002-09-05 17:54 ` Eric E Moore [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=87fzwo1fv6.fsf@dyn006239.shef.ac.uk \
--to=e.e.moore@sheffield.ac.uk \
/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).