catcode change in macros
Hi, I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes. \def\????ax{@@@@ax} \bgroup \catcode`\%=11 \catcode`\:=14 \gdef\setupaxis {\catcode`\%=11 \catcode`\:=14 \dodoubleargument\dosetupaxis} \gdef\dosetupaxis[#1][#2]: {\catcode`\%=11 \catcode`\:=14 \def\docommand##1{\getparameters[\????ax##1][#2]}: \catcode`\%=14 \catcode`\:=12 \processcommalist[#1]\docommand} \egroup \setupaxis [\c!x,\c!y] [\c!format=%d] Regards, Wolfgang
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes.
I think it will be cleaner to use catcode tables. See syst-cat.mkiv. Aditya
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes.
I think it will be cleaner to use catcode tables. See syst-cat.mkiv.
and syst-cat.tex Aditya
Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes.
I think it will be cleaner to use catcode tables. See syst-cat.mkiv.
and syst-cat.tex
I already know them but you're right, it's better to use them and avoid low level code. P.S. Should I now send all my questions to you or still use the mailing list :) Thanks and regards, Wolfgang
Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes.
I think it will be cleaner to use catcode tables. See syst-cat.mkiv.
and syst-cat.tex
I keep now my low level solution but with fewer lines. To help other users with the same question I present here my solution: \def\????ax{@@@@ax} \def\setupaxis {\catcode`\%\@@letter \dodoubleargument\dosetupaxis} \def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \catcode`\%\@@comment \processcommalist[#1]\docommand} \setupaxis [\c!x,\c!y] [\c!format=%d] Regards, Wolfgang
On Sat, 15 Nov 2008, Wolfgang Schuster wrote:
Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes.
I think it will be cleaner to use catcode tables. See syst-cat.mkiv.
and syst-cat.tex
I keep now my low level solution but with fewer lines.
Even though you are still using the mailling list, I will reply :-)
To help other users with the same question I present here my solution:
\def\????ax{@@@@ax}
\def\setupaxis {\catcode`\%\@@letter \dodoubleargument\dosetupaxis}
\def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \catcode`\%\@@comment \processcommalist[#1]\docommand}
\setupaxis [\c!x,\c!y] [\c!format=%d]
Here you are assuming that whenever \setupaxis will be used, the catcode of % is comment. This may not be the case. You can of course, store the inital catcode of % and then restore it later, as done by many LaTeX packages. The main advantage of catcode tables is that you can do \pushcatcodetable, and \popcatcodetable, and not do the book keeping yourself. Here is a solution using catcodetables: \unprotect % A mixture of \startcatcodetable and \extendcatcodetable \long\def\startchangecatcodetable#1#2#3\stopchangecatcodetable {\bgroup \catcodetable\scratchcatcodetable \catcodetable#1\relax #3% \savecatcodetable#2\relax \egroup} \newcatcodetable \LUAstringcatcodes \startchangecatcodetable \ctxcatcodes \LUAstringcatcodes \catcode`\%\@@letter \stopchangecatcodetable \protect \starttext \pushcatcodetable \catcodetable\LUAstringcatcodes % Does this print Hello world \popcatcodetable \stoptext So, you code now becomes \unprotect \def\????ax{@@@@ax} \def\setupaxis {\pushcatcodetable \catcodetable\LUAstringcatcodes \dodoubleargument\dosetupaxis} \def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \popcatcodetable \processcommalist[#1]\docommand} \setupaxis [\c!x,\c!y] [\c!format=%d] Hans, do you think that something like \startchangecatcodetable should be added to the core. An old definition of \extendcatcodetable almost does that, but does not provide a name to the resulatant catcodetable. Aditya
Aditya Mahajan wrote:
On Sat, 15 Nov 2008, Wolfgang Schuster wrote:
Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes. I think it will be cleaner to use catcode tables. See syst-cat.mkiv. and syst-cat.tex I keep now my low level solution but with fewer lines.
Even though you are still using the mailling list, I will reply :-)
To help other users with the same question I present here my solution:
\def\????ax{@@@@ax}
\def\setupaxis {\catcode`\%\@@letter \dodoubleargument\dosetupaxis}
\def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \catcode`\%\@@comment \processcommalist[#1]\docommand}
\setupaxis [\c!x,\c!y] [\c!format=%d]
Here you are assuming that whenever \setupaxis will be used, the catcode of % is comment. This may not be the case. You can of course, store the inital catcode of % and then restore it later, as done by many LaTeX packages.
The main advantage of catcode tables is that you can do \pushcatcodetable, and \popcatcodetable, and not do the book keeping yourself. Here is a solution using catcodetables:
\unprotect
% A mixture of \startcatcodetable and \extendcatcodetable \long\def\startchangecatcodetable#1#2#3\stopchangecatcodetable {\bgroup \catcodetable\scratchcatcodetable \catcodetable#1\relax #3% \savecatcodetable#2\relax \egroup}
\newcatcodetable \LUAstringcatcodes
\startchangecatcodetable \ctxcatcodes \LUAstringcatcodes \catcode`\%\@@letter \stopchangecatcodetable
\protect
\starttext
\pushcatcodetable \catcodetable\LUAstringcatcodes % Does this print Hello world \popcatcodetable
\stoptext
So, you code now becomes
\unprotect \def\????ax{@@@@ax}
\def\setupaxis {\pushcatcodetable \catcodetable\LUAstringcatcodes \dodoubleargument\dosetupaxis}
\def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \popcatcodetable \processcommalist[#1]\docommand}
\setupaxis [\c!x,\c!y] [\c!format=%d]
Hans, do you think that something like \startchangecatcodetable should be added to the core. An old definition of \extendcatcodetable almost does that, but does not provide a name to the resulatant catcodetable.
i wonder if change is the right name, isn't it more cloning? anyhow, keep in mind that in mkiv we print back to tex every now and then and then we use one of the predefined catcode tables. Another option is: [\c!format=\letterpercent d] Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Am 15.11.2008 um 21:41 schrieb Hans Hagen:
Aditya Mahajan wrote:
On Sat, 15 Nov 2008, Wolfgang Schuster wrote:
Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
On Fri, 14 Nov 2008, Aditya Mahajan wrote:
On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
Hi,
I make in a module the comment sign a simple letter to pass number formats to a lua function and want to know if should use another (better) way to change the catodes. I think it will be cleaner to use catcode tables. See syst- cat.mkiv. and syst-cat.tex I keep now my low level solution but with fewer lines.
Even though you are still using the mailling list, I will reply :-)
To help other users with the same question I present here my solution:
\def\????ax{@@@@ax}
\def\setupaxis {\catcode`\%\@@letter \dodoubleargument\dosetupaxis}
\def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \catcode`\%\@@comment \processcommalist[#1]\docommand}
\setupaxis [\c!x,\c!y] [\c!format=%d]
Here you are assuming that whenever \setupaxis will be used, the catcode of % is comment. This may not be the case. You can of course, store the inital catcode of % and then restore it later, as done by many LaTeX packages.
Right but I dropped catcode tables because I had a problems with them (see below).
The main advantage of catcode tables is that you can do \pushcatcodetable, and \popcatcodetable, and not do the book keeping yourself. Here is a solution using catcodetables:
I can't use it in my macro. \unprotect \long\def\startchangecatcodetable#1#2#3\stopchangecatcodetable {\bgroup \catcodetable\scratchcatcodetable \catcodetable#1\relax #3% \savecatcodetable#2\relax \egroup} \newcatcodetable \LUAstringcatcodes \startchangecatcodetable \ctxcatcodes \LUAstringcatcodes \catcode`\%\@@letter \stopchangecatcodetable \def\????ax{@@@@ax} \def\setupaxis {\pushcatcodetable \catcodetable\LUAstringcatcodes \dodoubleargument\dosetupaxis} \def\dosetupaxis[#1][#2]% {\def\docommand##1{\getparameters[\????ax##1][#2]}% \popcatcodetable \processcommalist[#1]\docommand} \setupaxis [\c!x,\c!y] [\c!format=%d] \protect \starttext \getvalue{@@@@axxformat} \stoptext
Hans, do you think that something like \startchangecatcodetable should be added to the core. An old definition of \extendcatcodetable almost does that, but does not provide a name to the resulatant catcodetable.
i wonder if change is the right name, isn't it more cloning?
anyhow, keep in mind that in mkiv we print back to tex every now and then and then we use one of the predefined catcode tables.
I save \@@@@axxformat in a Lua table and use it only in string.format, it never appears in the output.
Another option is:
[\c!format=\letterpercent d]
No interest, if I want %d to format my string in Lua I want to write also in this format in TeX. Wolfgang
participants (3)
-
Aditya Mahajan -
Hans Hagen -
Wolfgang Schuster