1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
|
% language=us
% \enabletrackers[context*]
\usemodule[present-boring,abbreviations-logos]
\startdocument
[title={IMPLEMENTERS},
banner={an old feature still evolving},
location={context\enspace {\bf 2020}\enspace meeting}]
\starttitle[title=Interfacing with \LUA]
\startitemize
\startitem
Quite some activity is delegated to \LUA.
\stopitem
\startitem
Normally the initiative is at the \TEX\ end.
\stopitem
\startitem
We can set variables or call functions etc.
\stopitem
\startitem
We can parameters to function calls.
\stopitem
\startitem
From the \LUA\ end we can use scanners to pick up data.
\stopitem
\startitem
We provide some consistent interfaces for doing all that.
\stopitem
\startitem
From \TEX\ to \LUA\ we use \type {\ctxlua{...}} and friends.
\stopitem
\startitem
From \LUA\ to \TEX\ we use \type {context(...)} and alike.
\stopitem
\startitem
For adding functionality we use so called implementers.
\stopitem
\stopitemize
\stoptitle
\starttitle[title=Calling \LUA]
\startbuffer
\ctxlua{context("ok")}
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\ctxlua{context(2 * tokens.scanners.integer())} 10
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\startluacode
function document.MyThing() context(2 * tokens.scanners.integer()) end
\stopluacode
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\ctxlua{document.MyThing()} 20 \quad
\ctxlua{document.MyThing()} 30 \quad
\ctxlua{document.MyThing()} 40
\stopbuffer
\typebuffer \getbuffer
\stoptitle
\starttitle[title=Streamlining \LUA]
\startbuffer
\startluacode
interfaces.implement {
name = "MyThing",
public = true,
arguments = "integer",
actions = function(i) context(i * 2) end,
-- actions = { function(i) return i * 2 end, context },
}
\stopluacode
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\MyThing 20 \quad \MyThing 30 \quad \MyThing 40
\stopbuffer
\typebuffer \getbuffer
\stoptitle
\starttitle[title=Making commands]
\startbuffer
\startluacode
interfaces.implement {
name = "MyRoot",
public = true,
actions = function()
local a = tokens.scanners.integer()
if not tokens.scanners.keyword("of") then
-- tex.error("the keyword 'of' expected")
end
local b = tokens.scanners.integer()
context("%0.6N",math.sqrt(b,a))
end,
}
\stopluacode
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\MyRoot 2 of 40 \quad \MyRoot 3 60
\stopbuffer
\typebuffer \getbuffer
\stoptitle
\starttitle[title=Scanners]
There are lots of scanners: \blank
\startalign[flushleft,broad] \tttf
\cldcontext { table.concat ( table.sortedkeys (tokens.scanners), " " ) }
\stopalign
\stoptitle
\starttitle[title=A more complex example]
Let's implement a matcher: \blank
\startbuffer
\doloopovermatch {(.)} {luametatex} { [#1] }
\stopbuffer
\typebuffer \getbuffer
\startbuffer
\doloopovermatch {([\letterpercent w]+)} {\cldloadfile{tufte.tex}} { [#1] }
\stopbuffer
\typebuffer \getbuffer
\stoptitle
\starttitle[title=A more complex example (\TEX)]
Here is the macro definition of this loop: \blank
\starttyping
\protected\def\doloopovermatch#1#2#3%
{\pushmacro\matchloopcommand
\def\matchloopcommand##1##2##3##4##5##6##7##8##9{#3}%
\ctxluamatch\matchloopcommand{#1}{#2}%
\popmacro\matchloopcommand}
\stoptyping
\startitemize
\startitem The pushing and popping makes it possible to nest this macro. \stopitem
\startitem The definition of the internal match macro permits argument references. \stopitem
\stopitemize
\stoptitle
\starttitle[title=A more complex example (\LUA)]
At the \LUA\ end we use an implementer: \blank
\starttyping[style=\small\tt]
local escape = function(s) return "\\" .. string.byte(s) end
interfaces.implement {
name = "ctxluamatch",
public = true,
usage = "value",
actions = function()
local command = context[tokens.scanners.csname()]
local pattern = string.gsub(tokens.scanners.string(),"\\.",escape)
local input = string.gsub(tokens.scanners.string(),"\\.",escape)
for a, b, c, d, e, f, g, h, i in string.gmatch(input,pattern) do
command(a, b or "", c or "", d or "", e or "", f or "", g or "",
h or "", i or "")
end
return tokens.values.none
end,
}
\stoptyping
So what does the \type {usage} key tells the implementer?
\stoptitle
\starttitle[title=Value functions]
Normally we pipe back verbose strings that are interpreted as if they were
files. Value functions are different;
\startitemize
\startitem
The return value indicates what gets fed back in the input.
\stopitem
\startitem
This can be: \cldcontext { table.concat(token.getfunctionvalues(), ", ", 0) }.
\stopitem
\startitem
When possible an efficient token is injected.
\stopitem
\startitem
Value function can check if they are supposed to feed back a value.
\stopitem
\startitem
So, they can be used as setters and getters.
\stopitem
\startitem
A variant is a function that is seen as conditional.
\stopitem
\startitem
In (simple) tracing they are presented as primitives.
\stopitem
\startitem
They are protected against user overload (aka: frozen).
\stopitem
\startitem
All this is experimental and might evolve.
\stopitem
\stopitemize
\stoptitle
\starttitle[title=So, let's step up a level]
Say that we want an expandable command:
\startbuffer
\edef\foo{\doloopovermatched{.}{123}{(#1)}} \meaning\foo
\stopbuffer
\typebuffer \blank \getbuffer \blank
Or nested:
\startbuffer
\edef\foo {%
\doloopovermatched {(..)} {123456} {%
\doloopovermatched {(.)(.)} {#1} {%
[##1][##2]%
}%
}%
} \meaning\foo
\stopbuffer
\typebuffer \blank \getbuffer \blank
\stoptitle
\starttitle[title=So, let's step up a level]
Compare:
\starttyping[style=\small\tt]
\protected\def\doloopovermatch#1#2#3%
{\pushmacro\matchloopcommand
\def\matchloopcommand##1##2##3##4##5##6##7##8##9{#3}%
\ctxluamatch\matchloopcommand{#1}{#2}%
\popmacro\matchloopcommand}
\stoptyping
With:
\starttyping[style=\small\tt]
\def\doloopovermatched#1#2#3%
{\beginlocalcontrol
\pushmacro\matchloopcommand
\def\matchloopcommand##1##2##3##4##5##6##7##8##9{#3}%
\endlocalcontrol
\the\ctxluamatch\matchloopcommand{#1}{#2}%
\beginlocalcontrol
\popmacro\matchloopcommand
\endlocalcontrol}
\stoptyping
Local control hides the assignments (it basically nests the mail loop).
\stoptitle
\starttitle[title=A few teasers (\TEX)]
\starttyping[style=\small\tt]
\doloopovermatch {(\letterpercent d+)} {this 1 is 22 a 333 test} { [#1] }
\doloopovermatch {(\letterpercent w+) *(\letterpercent w*)} {aa bb cc dd} {
[
\doloopovermatch{(\letterpercent w)(\letterpercent w)} {#1} {(##1 ##2)}
\doloopovermatch{(\letterpercent w)(\letterpercent w)} {#2} {(##1 ##2)}
]
}
\doloopovermatch
{(.-)\letterpercent{\bf (.-)\letterpercent}(.*)}
{this is {\bf a} test}
{#1{\it not #2}#3}
\stoptyping
\stoptitle
\starttitle[title=A few teasers (\LUA)]
\starttyping[style=\small\tt]
interfaces.implement {
name = "bitwisexor", public = true, usage = "value", actions =
function(what)
local a = tokens.scanners.cardinal()
scankeyword("with")
local b = tokens.scanners.cardinal()
if what == "value" then
return tokens.values.cardinal, a ~ b
else
logs.texerrormessage("you can't use \\bitwiseor this way")
end
end
}
interfaces.implement {
name = "ifbitwiseand", public = true, usage = "condition", actions =
function(what)
local a = tokens.scanners.cardinal()
local b = tokens.scanners.cardinal()
return tokens.values.boolean, (a & b) ~= 0
end
}
\stoptyping
\stoptitle
\starttitle[title=Questions and more examples]
More examples will be given in the editor.
\stoptitle
\stopdocument
% \doloopovermatch {(\letterpercent w+) *(\letterpercent w*)} {aa bb cc dd} {
% [
% \doloopovermatch{(\letterpercent w)(\letterpercent w)} {#1} {(##1 ##2)}
% \doloopovermatch{(\letterpercent w)(\letterpercent w)} {#2} {(##1 ##2)}
% ]
% }
% \doloopovermatch {(\letterpercent d+)} {this 1 is 22 a 333 test} { [#1] }
% \testfeatureonce{10000}{\doloopovermatch {(\letterpercent d+)} {this 1 is 22 a 333 test} {}} \elapsedtime
% \doloopovermatch
% {(.-)\letterpercent{\bf (.-)\letterpercent}(.*)}
% {this is {\bf a} test}
% {#1{\it not #2}#3}
% \doloopovermatch {([\letterpercent w]+)} {\cldloadfile{tufte.tex}} { [#1] }
% \testfeatureonce{100}{\doloopovermatch {([\letterpercent w]+)}{\cldloadfile{tufte.tex}} {}} \elapsedtime
|