From: Holger Peters <holger.peters@posteo.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: guile-user@gnu.org
Subject: Re: Namespace confusion/pollution in languages implemented via Guile's compile-tower
Date: Thu, 26 Nov 2020 17:27:52 +0100 [thread overview]
Message-ID: <f4f6510726492643c477c5208bfe49c5@posteo.de> (raw)
In-Reply-To: <875z6gj32i.fsf@web.de>
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.
I had a look at the guile codebase proposed a patch that would unify
the behaviour of REPL and script execution:
https://lists.gnu.org/archive/html/guile-devel/2020-11/msg00004.html
---
Holger Peters <holger.peters@posteo.de>
Am 07.11.2020 21:59 schrieb Dr. Arne Babenhauserheide:
> holger.peters@posteo.de writes:
>> It seems that in the REPL, Guile injects the `guile-user' module
>> directly whereas when called with `-s` and a script guile uses the
>> module provided with `#:make-default-environment'. That seems strange
>> because overall I would expect REPL environments and non-REPL
>> environments to be roughly the same.
>>
>> So, is this a bug? Works as intended? And if this is intended in this
>> way is there a workaround to make REPL and script exeution to behave
>> the same (preferably without namespace `pollution').
>
>
> Best wishes,
> Arne
next prev parent reply other threads:[~2020-11-26 16:27 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 [this message]
2020-11-26 18:15 ` Dr. Arne Babenhauserheide
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=f4f6510726492643c477c5208bfe49c5@posteo.de \
--to=holger.peters@posteo.de \
--cc=arne_bab@web.de \
--cc=guile-user@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).