From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Holger Peters <holger.peters@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: Namespace confusion/pollution in languages implemented via Guile's compile-tower
Date: Thu, 26 Nov 2020 19:15:22 +0100 [thread overview]
Message-ID: <87sg8wkmrp.fsf@web.de> (raw)
In-Reply-To: <f4f6510726492643c477c5208bfe49c5@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Holger Peters <holger.peters@posteo.de> writes:
> Hi,
>
>> This is as intended.
>
> Do you have a rationale for this intention? I have been thinking
> about this for weeks now, and I still cannot come up with a scenario
> when I would like this behaviour. That is if I'd load a lua-on-guile
> REPL, I wouldn't like to have Lua symbols missing and Scheme symbols
> present.
The intention is that when in the REPL you have some extra-tools that a
typical script does not need.
Looking at boot-9, guile-user mostly adds compile and compile-file.
You’ll want to be able to compile stuff in the REPL, but scripts should
not need to worry about that (because they get auto-compiled anyway).
The intention is not to provide Scheme-tools to Lua, but to provide
extended Scheme-tools when you’re in the REPL.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2020-11-26 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 11:54 Namespace confusion/pollution in languages implemented via Guile's compile-tower holger.peters
2020-11-07 20:59 ` Dr. Arne Babenhauserheide
2020-11-26 16:27 ` Holger Peters
2020-11-26 18:15 ` Dr. Arne Babenhauserheide [this message]
2020-11-09 7:48 ` Linus Björnstam
2020-11-09 12:30 ` Felix Thibault
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=87sg8wkmrp.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=holger.peters@posteo.de \
/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).