From: Jean Louis <bugs@gnu.support>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master b72f885: Make dlet work like let, not let*
Date: Tue, 21 Sep 2021 07:19:23 +0300 [thread overview]
Message-ID: <YUldS+SPJRSnatql@protected.localdomain> (raw)
In-Reply-To: <87y27rhwp0.fsf@gnu.org>
* Tassilo Horn <tsdh@gnu.org> [2021-09-20 22:31]:
> Jean Louis <bugs@gnu.support> writes:
>
> > I am user and I do not expect it to work as `let' because `dlet' is
> > supposed to make temporarily global variables. Now it doesn't work:
> >
> > (dlet ((wrs::variables (make-hash-table :test 'equal))
> > (wrs::_ (puthash "areas_name" "Hyperscope" wrs::variables)))
> > )
> >
> > error: let: Symbol’s value as variable is void: wrs::variables
> >
> > That is IMHO wrong, as it is supposed to bind variables
> > dynamically:
>
> Being able to refer to variables earlier in the same binding form has
> nothing do with dynamic binding. `let' and `dlet' don't support that,
> `let*' does, and as Mattias said, there could be a `dlet*' if someone
> needs it.
>
> What dlet allows you is to bind variables dynamically which are no
> special variable (are not declared with defvar). For example:
>
> --8<---------------cut here---------------start------------->8---
> (defun foo ()
> some-var)
>
> (foo) ;; Lisp error: (void-variable some-var)
>
> (dlet ((some-var 17))
> (foo)) ;=> 17
> --8<---------------cut here---------------end--------------->8---
>
> But instead of dlet you could just as well defvar some-var and use a
> normal `let' instead.
>
> Why can't you defvar wrs::variables? Or maybe it already is? In that
> case, you could just replace `dlet' with `let*'.
Thanks Tassilo for the tip, though I have tried to use `defvar' and
`let*' and that does not work in my case. I cannot technically explain
it why. Practically, lexical binding script is calling in my case
dynamical binding function.
By using `defvar' and subsequently `let*' I can avoid the first error.
I cannot however get the variables to pass over to the function in
dynamical binding script `rcd-template-eval' that is supposed to work
with variables.
This worked with `dlet' before, not it does not work.
Developer changed `dlet' to fit whatever programming habits, but
deleted the functionality of `dlet*'
I really need it.
rcd-template-eval: `eval' error: (void-variable languages_extension)
for match: 'languages_extension'rcd-template-eval: `eval' error:
(void-variable areas_id) for match: 'areas_id'rcd-template-eval:
`eval' error: (void-variable pages_categories) for match:
'pages_categories'rcd-template-eval: `eval' error: (void-variable
pages_id) for match: 'pages_id'rcd-template-eval: `eval' error:
(void-variable pages_copypage) for match:
'pages_copypage'rcd-template-eval: `eval' error: (void-variable
areas_company) for match: 'areas_company'rcd-template-eval: `eval'
error: (void-variable areas_url) for match:
'areas_url'rcd-template-eval: `eval' error: (void-variable
wrs::keywords) for match: '(xml-escape
wrs::keywords)'rcd-template-eval: `eval' error: (void-variable
wrs::description) for match: '(xml-escape
wrs::description)'rcd-template-eval: `eval' error: (void-variable
wrs::description) for match: '(xml-escape
wrs::description)'rcd-template-eval: `eval' error: (void-variable
open-graph-type) for match: 'open-graph-type'rcd-template-eval: `eval'
error: (void-variable areas_url) for match:
'areas_url'rcd-template-eval: `eval' error: (void-variable
wrs::description) for match: '(xml-escape
wrs::description)'rcd-template-eval: `eval' error: (void-variable
headerstuff) for match: 'headerstuff'rcd-template-eval: `eval' error:
(void-variable after_content) for match:
'after_content'rcd-template-eval: `eval' error: (void-variable
inquiry) for match: 'inquiry'rcd-template-eval: `eval' error:
(void-variable footerstuff) for match: 'footerstuff'Invalid face
reference: mail-double-quoted-text-face
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-09-21 4:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 16:10 master b72f885: Make dlet work like let, not let* Eli Zaretskii
2021-08-03 13:03 ` Mattias Engdegård
2021-08-03 13:33 ` Eli Zaretskii
2021-08-03 15:21 ` Mattias Engdegård
2021-08-03 15:58 ` Eli Zaretskii
2021-08-03 17:19 ` Stefan Monnier
2021-08-03 17:50 ` Eli Zaretskii
2021-08-03 18:50 ` Stefan Monnier
2021-08-04 11:27 ` Eli Zaretskii
2021-08-04 11:35 ` Lars Ingebrigtsen
2021-08-04 11:46 ` Mattias Engdegård
2021-08-04 12:16 ` Eli Zaretskii
2021-08-04 12:48 ` Mattias Engdegård
2021-08-04 12:15 ` Eli Zaretskii
2021-08-04 3:09 ` Michael Heerdegen
2021-08-04 11:40 ` Eli Zaretskii
2021-09-20 17:08 ` Jean Louis
2021-09-20 17:02 ` Jean Louis
2021-09-20 16:56 ` Jean Louis
2021-09-20 19:16 ` Tassilo Horn
2021-09-21 4:19 ` Jean Louis [this message]
2021-09-21 6:31 ` Tassilo Horn
2021-09-21 7:17 ` Jean Louis
2021-09-21 7:50 ` Tassilo Horn
2021-09-21 9:31 ` Jean Louis
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YUldS+SPJRSnatql@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=tsdh@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).