From: Ihor Radchenko <email@example.com>
To: Zelphir Kaltstahl <firstname.lastname@example.org>, Bastien <email@example.com>
Cc: Bruno Barbier <firstname.lastname@example.org>, email@example.com
Subject: [BUG] Inconsistent global/local :var assignments in ob-* for lisps and non-lisps (was: org-babel guile source block bug in handling multiple values)
Date: Thu, 09 Mar 2023 13:04:05 +0000 [thread overview]
Message-ID: <87v8jaoz3u.fsf@localhost> (raw)
Zelphir Kaltstahl <firstname.lastname@example.org> writes:
> I am not sure (let ...) is a correct wrapper for noweb included source blocks.
> What, if I write a (define ...) in my source block and want to use that source
> block via noweb in another source block? Expected behavior I think would be to
> be able to access those variables in other source blocks, since they are defined
> on a top level in an earlier source block, but if they are wrapped in a (let
> ...), that would make them only available in the (let ...)? It seems to me, that
> the simple wrapping with a (let ...) might not be the right thing to do. Testing
> #+name: scheme-defs
> #+begin_src scheme :eval query-export :noweb strip-export :session myguile :results output replace drawer :var x=1 :var y=2
> (define a x)
> (define b y)
> #+name: scheme-time
> #+begin_src scheme :eval query-export :noweb strip-export :session myguile :results output replace drawer
> (simple-format #t "~a ~a\n" a b)
> Indeed, that also does not work.
I just checked ob-C, ob-shell, ob-emacs-lisp, and ob-clojure.
Non-lisps appear to assign the values globally.
In contrast, all the lisp babel backends are using let-bindings.
Considering the existing inconsistency, and the raised bug I'd be in
favor of making variable assignments global in all the lisp babel
The only possible exception is ob-emacs-lisp. Executing elisp code is
done in current Elisp session and thus using global variable assignments
may be tricky. Unless we juggle with multiple obarrays.
> I guess I did never hit this problem earlier, because I "oursourced" my imports
> and in imports I do not need any :var header arguments.
> I've asked on the Guile IRC channel and something interesting is the case here
> (thanks for clearing it up flatwhatson!) and I understand it as follows:
> Imports inside (let ...) work. It is just that let-values is a macro and macros
> are expanded before execution time. However, Guile gets to the body of the
> wrapping (let ...) at execution time. That means, that when Guile gets to
> evaluate the body of the let, it does not expand the let-values, because it is
> already at execution time and no longer at macro expansion time. The import
> might import the let-values form, or might not, but it is already too late to
> expand the (let-values ...).
So, apparently using `let' is not universally safe in Guile.
> OK, the question is though, whether org should wrap anything in a (let ...) at
> all. During discussion on the Guile IRC, some points against let-wrapping were
> brought up:
> (1) The presence of a :var header argument currently determines, whether the
> code in the source block is wrapped with a (let ...). One argument for that was,
> that this way the variables do not leak. But this also decides, whether other
> things leak. For example (import ...) or (define ...). Should :var decide,
> whether bindings created with (define ...) are visible in other source blocks
> including the source block with the :var header arguments? It seems like a
> responsibility :var should not have and definitely is unexpected for the user.
This is something Guile-specific. In Elisp, let-binding still allows
`defun' or `defvar'.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-03-09 13:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 11:27 org-babel guile source block bug in handling multiple values Zelphir Kaltstahl
2023-03-07 14:36 ` Ihor Radchenko
2023-03-07 15:18 ` Zelphir Kaltstahl
2023-03-07 19:52 ` Bruno Barbier
2023-03-08 0:55 ` Zelphir Kaltstahl
2023-03-08 19:38 ` Bruno Barbier
2023-03-09 0:44 ` Zelphir Kaltstahl
2023-03-09 13:04 ` Ihor Radchenko [this message]
2023-03-10 10:39 ` [BUG] Inconsistent global/local :var assignments in ob-* for lisps and non-lisps (was: org-babel guile source block bug in handling multiple values) Zelphir Kaltstahl
2023-03-11 9:58 ` Ihor Radchenko
2023-03-11 18:30 ` Zelphir Kaltstahl
2023-03-12 11:33 ` Ihor Radchenko
2023-03-19 13:50 ` [PATCH] lisp/ob-scheme.el Zelphir Kaltstahl
2023-03-22 10:43 ` Ihor Radchenko
2023-03-25 14:34 ` Zelphir Kaltstahl
2023-03-26 9:32 ` Ihor Radchenko
2023-04-25 12:28 ` Ihor Radchenko
2023-04-29 11:08 ` Zelphir Kaltstahl
2023-03-09 13:10 ` org-babel guile source block bug in handling multiple values Ihor Radchenko
2023-03-10 10:42 ` Zelphir Kaltstahl
2023-03-11 10:18 ` Ihor Radchenko
2023-06-02 13:11 ` Ihor Radchenko
2023-03-09 13:11 ` Ihor Radchenko
2023-03-09 14:21 ` Daniel Kraus
2023-03-10 11:57 ` Ihor Radchenko
2023-03-10 10:45 ` Zelphir Kaltstahl
2023-03-08 1:13 ` Zelphir Kaltstahl
2023-03-08 8:55 ` Ihor Radchenko
2023-03-07 15:44 ` Max Nikulin
2023-03-07 21:41 ` Rudolf Adamkovič
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).