From: Tom Lord <lord@regexps.com>
Cc: tb@becket.net
Subject: Re: :export vs. define-public
Date: Wed, 4 Sep 2002 19:05:05 -0700 (PDT) [thread overview]
Message-ID: <200209050205.TAA19305@morrowfield.regexps.com> (raw)
In-Reply-To: <87y9ahjl33.fsf@becket.becket.net> (tb@becket.net)
Oooo -- what a zinger.
-t
Cc: guile-devel@gnu.org
X-Reply-Permission: Posted or emailed replies to this message constitute
permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51 63 28 EB DA E6 44 E5 5E EC F3 04 26 4E BF 1A 92
X-Zippy-Says: They don't hire PERSONAL PINHEADS, Mr. Toad!
From: tb@becket.net (Thomas Bushnell, BSG)
Date: 04 Sep 2002 18:12:32 -0700
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
Content-Type: text/plain; charset=us-ascii
X-UIDL: "fW!!D:O"!2?;"!RLC!!
Tom Lord <lord@regexps.com> writes:
> > define-public is still there too.
>
>
> Having both seems like an invitation to subtle errors.
Ah! So after your plea that it's really irrelevant, it turns out that
you think only one should exist. Seems like a mistake to me. As you
rightly point out, they represent different styles of module design,
and there's no particular reason we should support only one.
The solution to subtle errors is bugfixing. The semantics, at least,
are quite clear.
_______________________________________________
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 2:05 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 [this message]
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=200209050205.TAA19305@morrowfield.regexps.com \
--to=lord@regexps.com \
--cc=tb@becket.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).