From: tb@becket.net (Thomas Bushnell, BSG)
Cc: guile-devel@gnu.org
Subject: Re: :export vs. define-public
Date: 04 Sep 2002 17:33:42 -0700 [thread overview]
Message-ID: <87lm6hl1g9.fsf@becket.becket.net> (raw)
In-Reply-To: <200209050041.RAA18955@morrowfield.regexps.com>
Tom Lord <lord@regexps.com> writes:
> Those two approaches (:export vs. define-public) to public v. private
> module contours are isomorphic, so what's the big deal?
There is no big deal. What makes you think there is? Only
define-public is documented. :export is not, nor is the more local
(export ...) form that Marius recently mentioned.
> Historically, I suspect that some module system changes made after the
> Cygnus releases were motivated in part because they made the Guile
> module system look more like S48 or some other famous schemes. And as
> we all know, those other systems reek of the scent of perfection (or
> at least, a perfection-style cologne). But that's just speculation,
> on my part. I'm aware that module system changes were originally
> argued (vaguely) for in terms of support for compilation.
I like perfection. I have access to many many "just do it, screw
perfection" systems. I'm tired of them.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-05 0:33 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 [this message]
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
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=87lm6hl1g9.fsf@becket.becket.net \
--to=tb@becket.net \
--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).