ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Henri Menke via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: protected macro vs protected luacall
Date: Fri, 27 Jan 2023 11:01:59 +0100	[thread overview]
Message-ID: <23eb2bf7-6b9c-1ff5-31fe-6d062f900c63@freedom.nl> (raw)
In-Reply-To: <2151cdb6c742a9f5db7e540bb65095729bde86bc.camel@henrimenke.de>

On 1/27/2023 10:35 AM, Henri Menke via ntg-context wrote:

> Thanks, this is indeed the workaround that I currently use. However,
> the downside is that this has to tokenize the contents of \directlua
> every time (and is therefore susceptible to surrounding \catcode
> shenanigans) and it expands in at minimum two steps, whereas a luacall
> always expands in a single step. But I guess that's what I will have to
> live with.
on my 2018 laptop, with

   function FoO() end

this

   \directlua{FoO()}}

takes 0.0000014 seconds so probably the least of your worries compared 
to other macro and lua magic

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
___________________________________________________________________________________

  reply	other threads:[~2023-01-27 10:01 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
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 [this message]
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=23eb2bf7-6b9c-1ff5-31fe-6d062f900c63@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).