From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Document top-level pseudo-hygiene
Date: Tue, 25 Mar 2014 21:07:21 +0100 [thread overview]
Message-ID: <87bnwuqbye.fsf@pobox.com> (raw)
In-Reply-To: <87r47ugh9h.fsf@netris.org> (Mark H. Weaver's message of "Sun, 26 Jan 2014 23:50:34 -0500")
Hi :)
On Mon 27 Jan 2014 05:50, Mark H Weaver <mhw@netris.org> writes:
> "Andy Wingo" <wingo@pobox.com> writes:
>> commit 03dfed840b377a72191b6f125c106fdfd9e90a21
>> Author: Andy Wingo <wingo@pobox.com>
>> Date: Fri Jan 24 12:34:26 2014 +0100
>>
>> Document top-level pseudo-hygiene
>>
>> * doc/ref/api-macros.texi (Hygiene and the Top-Level): Add a section
>> documenting our pseudo-hygienic top-level names.
>
> As I've said before, I strenuously object to these novel semantics that
> you've invented. I believe this would be an ugly wart on Guile that we
> would have to support indefinitely, in violation of the standards,
> because its existence would encourage people to write code that depends
> upon it.
I think the hyperbole is a bit out of place. All semantics are invented
and novel at some point; that is not an argument against a thing. But
you object; OK.
> Now, to reduce the danger that a library author might unwittingly make
> the mistake you're (rightly) worried about, I suggest that we rig the
> compiler to issue a warning whenever an introduced toplevel identifier
> crosses a module boundary.
I don't think we know this information. WDYT about warning when
residualizing a fresh toplevel? Or even raising an error? Perhaps one
could configure this somehow.
I certainly do not want any fresh toplevels to be residualized within
Guile proper, and I expect the same goes for other projects as well.
Fresh toplevels are just a novel semantic some people invented that I
strenuously object to ;-)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2014-03-25 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1W7QOI-0001rc-JS@vcs.savannah.gnu.org>
2014-01-27 4:50 ` Document top-level pseudo-hygiene Mark H Weaver
2014-02-06 23:13 ` Ludovic Courtès
2014-03-25 20:07 ` Andy Wingo [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=87bnwuqbye.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@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).