From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: protected macro vs protected luacall
Date: Thu, 26 Jan 2023 23:07:03 +0100 [thread overview]
Message-ID: <1869090e-1269-9094-bba0-e24f470d48e1@freedom.nl> (raw)
In-Reply-To: <5f064f677e75ff498bbaa1045bba70620ed7bc0a.camel@henrimenke.de>
On 1/26/2023 9:33 PM, Henri Menke via ntg-context wrote:
> \directlua{
> userdata = userdata or {}
> function userdata.test()
> tex.print("\string\\numexpr 17\string\\relax")
> end
> }
>
> \tt
> \protected\def\test{\directlua{userdata.test()}}
> \meaning\test\par
> \edef\x{\test}\meaning\x\par
> \the\test
>
> \directlua{
> local t = lua.get_functions_table()
> t[\string#t + 1] = userdata.test
> token.set_lua("test", userdata.test, \string#t, "protected")
> }
> \meaning\test\par
> \edef\x{\test}\meaning\x\par
> \the\test
from the code it looks like we're talking plain luatex ...
\the is very selective and doesn't work for all primitives or macros
compare it to \number which accepts any number representation following
it while \the doesn't work ok 123
that said, your set_lua is wrong and passes a function as well as an index
\directlua{
lua.get_functions_table()[999] = function()
tex.print("\string\\numexpr 17\string\\relax")
end
token.set_lua("test", 999)
}
\the \test % needs the \numexpr
\number \test % doesn't
\count0 \test % needs the \numexpr
\count0=\test % doesn't
etc
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-01-26 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 20:33 Henri Menke via ntg-context
2023-01-26 22:07 ` Hans Hagen via ntg-context [this message]
2023-01-27 9:13 ` Henri Menke via ntg-context
2023-01-27 9:30 ` Hans Hagen via ntg-context
2023-01-27 9:35 ` Henri Menke via ntg-context
2023-01-27 10:01 ` Hans Hagen via ntg-context
2023-01-27 11:03 ` Henri Menke via ntg-context
2023-01-27 11:52 ` Hans Hagen via ntg-context
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=1869090e-1269-9094-bba0-e24f470d48e1@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/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 NNTP newsgroup(s).