From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Writing to .tuc directly from Lua
Date: Wed, 24 Mar 2021 12:33:52 -0500 [thread overview]
Message-ID: <CAKyqqaZujnxrmRw903oc0hAP9gF7dcLaCu=R3h+40SHykHggmw@mail.gmail.com> (raw)
In-Reply-To: <db17683f-884f-4389-7635-84ad695ad536@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1782 bytes --]
Hi, Hans. Here's my (miserably failing) attempt:
\definedataset[nicedata]
\starttext
\startluacode
local name = "nicedata"
-- For exposition only
local function dofactorial(n)
local function inner(c,m)
if m<2 then return c end
return inner(c*m, m-1)
end
return inner(1,n)
end
local function factorial(n)
local stringn = tostring(n)
if job.datasets.collected[name] then
return job.datasets.collected[name].factorial[stringn]
else
local mydata = {[stringn] = tostring(dofactorial(n))}
job.datasets.setdata{
name = name,
tag = "factorial",
data = mydata
}
return mydata[stringn]
end
end
interfaces.implement{
name = "factorial",
public = true,
arguments = {"string"},
actions = {tonumber, factorial, context}
}
\stopluacode
\factorial{7}
\stoptext
What happens is that, in each run, both the first and the second conditions
are met, so the compilation is twice as slow, the opposite result of what I
meant to do. How do I fix that?
Jairo
El mié, 24 de mar. de 2021 a la(s) 01:38, Hans Hagen (j.hagen@xs4all.nl)
escribió:
> On 3/24/2021 5:20 AM, Jairo A. del Rio wrote:
> > Thank you very much. It's useful, indeed. However, what I need is to
> > bypass TeX (Lua > .tuc) if possible, since all the data I need to handle
> > is generated with Lua scripts.
> datasets-001.tex in the test suite
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------
>
[-- Attachment #1.2: Type: text/html, Size: 4957 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-24 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 3:28 Jairo A. del Rio
2021-03-24 4:12 ` Aditya Mahajan
2021-03-24 4:20 ` Jairo A. del Rio
2021-03-24 6:38 ` Hans Hagen
2021-03-24 17:33 ` Jairo A. del Rio [this message]
[not found] ` <nycvar.YAK.7.78.908.2103241631460.1372067@nqv-guvaxcnq>
2021-03-24 21:00 ` Jairo A. del Rio
2021-03-24 21:47 ` Hans Hagen
2021-03-24 23:00 ` Jairo A. del Rio
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='CAKyqqaZujnxrmRw903oc0hAP9gF7dcLaCu=R3h+40SHykHggmw@mail.gmail.com' \
--to=jairoadelrio6@gmail.com \
--cc=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.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).