Wolfgang Schuster
Am 13.02.10 13:24, schrieb John Devereux:
I asked before why ConTeXt does not flag incorrect parameters, I seem to recall the answer was that it would slow things down too much. But a command line switch to do this would be very useful. Already available for MkIV (mult-chk.mkiv):
\starttext
\testfeatureonce{10000}{\getcheckedparameters[test][xx][a=b,c= d, e = f]} % 0.20 seconds
\enablecheckparameters
\testfeatureonce{10000}{\getcheckedparameters[test][xx][a=b,c= d, e = f]} % 0.35 seconds
\getcheckedparameters[test][xx][a=a] \getcheckedparameters[test][xx][b= b] \getcheckedparameters[test][xx][c = c] \getcheckedparameters[test][xx][d = d d , e = e ,f = f ] \getcheckedparameters[test][xx][g={oeps {oeps}}] \getcheckedparameters[test][xx][crap=whatever]
\startlines [a:\getvalue{xxa}][a] [b:\getvalue{xxb}][b] [c:\getvalue{xxc}][c] [d:\getvalue{xxd}][d d ] [e:\getvalue{xxe}][e ] [f:\getvalue{xxf}][f ] [g:\getvalue{xxg}][\detokenize\expandafter{\xxg}] \stoplines
\setvalidparameterkeys[test][crap]
\getcheckedparameters[test][xx][crap=whatever]
\stoptext
Wolfgang
Hi Wolfgang. That is a bit beyond me... I am guessing this means that there is now a facility whereby certain commands could be instrumented? In the future? What I was asking for was a general "switch" that could turn on parameter error checking for all commands. (Perhaps the work involved is too much). -- John Devereux