public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Using eval with environments and R7RS modules
Date: Mon, 30 Nov 2020 03:12:49 -0500	[thread overview]
Message-ID: <CABgWrqpN6r1x2pSHv4zaTJ390wis+dDKc=uJ4bH8CFhFGfLyZg@mail.gmail.com> (raw)
In-Reply-To: <d14eab69-8279-a012-5fed-dceca4d02d0a@bothner.com>

Thanks for the tip, Per.

That did tie me over, but it doesn't feel like a great way to fix it.

Would the right thing to do be to allow something like this?

(environment '((scheme base) (my library) ...))


Duncan.

On Mon, Nov 30, 2020 at 1:35 AM Per Bothner <per@bothner.com> wrote:

> On 11/29/20 10:21 PM, Duncan Mak via Kawa wrote:
> > I'm trying to use EVAL in a R7RS module. I'm having trouble specifying
> the
> > environment that contains the current bindings
> >
> > I could either use (environment '(scheme base)), but I don't see my own
> > functions, or (environment '(my library)) then I don't see something
> basic
> > like QUASIQUOTE.
> >
> > Is there a way for me to load multiple modules into the environment?
>
> One possible work-around is to have (my library) explicitly export
> the symbols that you need from (scheme base).
> --
>         --Per Bothner
> per@bothner.com   http://per.bothner.com/
>


-- 
Duncan.

  reply	other threads:[~2020-11-30  8:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  6:21 Duncan Mak
2020-11-30  6:35 ` Per Bothner
2020-11-30  8:12   ` Duncan Mak [this message]
2020-11-30 12:30     ` Per Bothner
2020-11-30 22:15       ` Duncan Mak
2020-11-30 10:13 ` Damien MATTEI
2020-11-30 12:21   ` Per Bothner
2020-11-30 18:09     ` Damien MATTEI
2020-12-02 14:58       ` Jamison Hope
2020-12-04  8:05         ` Damien MATTEI

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABgWrqpN6r1x2pSHv4zaTJ390wis+dDKc=uJ4bH8CFhFGfLyZg@mail.gmail.com' \
    --to=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /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).