“PCRE provides a feature called ‘callout’, which is a means of temporarily passing control to the caller of PCRE in the middle of pattern matching. The caller of PCRE provides an external function by putting its entry point in the global variable pcre_callout<\/code>.” <\/p><\/blockquote>\nCalling LuaTeX<\/h2>\n
OK, so how do we do that? There are two parts to this story: create a Lua function you want to call from C and create the C function which calls the Lua function.<\/p>\n
\n- From within LuaTeX, use
\\directlua{...}<\/code> to create a simple Lua function printy<\/code> that we are going to call from PCRE. This Lua function takes a string and sends it to LuaTeX via tex.print(). In these examples I sent LuaTeX a simple text string \"Yo! I was called!\"<\/code>, which LuaTeX then typeset. Of course, you could also send LuaTeX the string that was matched by PCRE!\n\r\n \\directlua{\r\n function printy (str)\r\n tex.print(str)\r\n end\r\n }\r\n<\/pre>\n<\/li>\n- The next part is to create the C code to call a Lua function. This C function is the callout that PCRE will call when it matches a string.\n
\r\n int mycallout(pcre_callout_block *cb){\r\n lua_State *L;\r\n L = cb->callout_data;\r\n if (L){\r\n lua_getglobal(cb->callout_data, "printy");\r\n if(!lua_isfunction(L,-1)) {\r\n lua_pop(L,1);\r\n return 0;\r\n }\r\n\r\n lua_pushstring(L, "Yo! I was called!"); \/* push 1st argument *\/\r\n \/* Now make the call to printy with 1 argument and 0 results*\/\r\n if (lua_pcall(L, 1, 0, 0) != 0) {\r\n \/\/ report your error \r\n return 0;\r\n }\r\n }\r\n return 0;\r\n}\r\n<\/pre>\nA few points here are worth noting. <\/p>\n
\n- From the PCRE documentation:
\n“The external callout function returns an integer to PCRE. If the value is zero, matching proceeds as normal. If the value is greater than zero, matching fails at the current point, but the testing of other matching possibilities goes ahead, just as if a lookahead assertion had failed. If the value is less than zero, the match is abandoned, the matching function returns the negative value”<\/p><\/blockquote>\n<\/li>\n
- The
lua_State<\/code> variable, *L<\/code>, is passed in via a mechanism I’ll outline below.<\/li>\n- The line
lua_getglobal(cb->callout_data, \"printy\")<\/code> does the main work of pushing the value of the gloabal variable printy<\/code> onto Lua’s stack. Of course, in effect this is a pointer to the function we defined in LuaTeX, and which we call through lua_pcall(...)<\/code>. Further details in the Lua documentation. <\/li>\n- The above code does near-zero error checking, it is purely to demonstrate the ideas!<\/li>\n<\/blockquote>\n<\/ul>\n<\/li>\n<\/ol>\n
Other PCRE bits and pieces<\/h2>\n
There are a few other points to consider, namely how do you setup the callout and how do you pass lua_State *L<\/code> to the callout? I’m not going to explain in great detail how all these parts hang together in a full application, simply point out some key pieces.<\/p>\n\n- You have to set the PCRE global variable
pcre_callout<\/code>, a function pointer, to your callout function. Simply, pcre_callout = mycallout;<\/code> Yes, it does work. Here, re<\/code> represents our compiled regular expression pattern. Note that you must use the PCRE_UTF8<\/code> option if you are searching UTF-8 encoded text.<\/li>\n- Before you can start searching, you need to “compile” your regular expression pattern.\n
\r\n re = pcre_compile(pattern,\r\n\t\t PCRE_UTF8|PCRE_UCP,\r\n\t\t &err_msg,\r\n\t\t &err,\r\n\t\t NULL);\r\n<\/pre>\n<\/li>\n
- Note, to use PCRE callouts you need to use the appropriate syntax in your regular expression; from the PCRE documentation, “Within a regular expression, (?C) indicates the points at which the external function is to be called.” Once you have compiled your search pattern, and done your error checking, you need to run the search engine using the compiled pattern and your target string (
s<\/code>) in the code below.\n<\/li>\n- \nThe next step is to create a pointer to something called a
pcre_callout_block<\/code>, which is a struct. This struct has a field called callout_data<\/code> which is a pointer into which you can store whatever you want to pass into the mycallout<\/code> function: here, I’m setting it to the lua_State<\/code> variable, L<\/code>. By doing this, each time PCRE matches a string and calls the callout funtion, the lua_State<\/code> variable, L<\/code> will be available for our use! Clearly, you’ll need to do this from within the appropriate function you call from LuaTeX. Once this is done you are ready to begin your searching using pcre_exec(...)<\/code>. <\/p>\n\r\n pcre_extra *p;\r\n p = (pcre_extra*) malloc(sizeof(pcre_extra));\r\n memset(p,0, sizeof(pcre_extra));\r\n p->callout_data = L;\r\n p->flags=PCRE_EXTRA_CALLOUT_DATA;\r\n res = pcre_exec(re,\r\n p,\r\n s,\r\n len,\r\n 0,\r\n 0,\r\n offsets,\r\n OVECMAX);\r\n<\/pre>\n<\/li>\n<\/ol>\nSummary<\/h1>\n
PCRE is a marvellous and powerful C library – with copious documentation that you’ll need to read very carefully! The ability to provide LuaTeX with a UTF-8-enabled regex engine could open the way to some useful applications, particularly when combined with LuaTeX’s own callback mechanism. In particular, the process_input_buffer<\/code> callback which allows you to change the contents of the line input buffer just before LuaTeX actually starts looking at it. The mind boggles at the possibilities!<\/p>\n","protected":false},"excerpt":{"rendered":"Introduction In this post I’m going to sketch out adding the free PCRE C library to LuaTeX through a DLL and outline how you can get PCRE to call LuaTeX! The following is just an outline of an experiment, not a tutorial on PCRE, and I’ve not tried this in a production environment. So, do […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,3],"tags":[],"class_list":["post-2428","post","type-post","status-publish","format-standard","hentry","category-luatex-c-code-windows-dlls","category-luatex"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2428","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2428"}],"version-history":[{"count":41,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2428\/revisions"}],"predecessor-version":[{"id":2695,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2428\/revisions\/2695"}],"wp:attachment":[{"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2428"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2428"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.readytext.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2428"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![](\"http:\/\/readytext.co.uk\/files\/cmake.png\")
<\/p>\n