John Devereux wrote:
Wolfgang Schuster <schuster.wolfg...@googlemail.com> writes:
Am 12.03.2009 um 15:06 schrieb John Devereux:
Michael Bynum <mdby...@gmail.com> writes:
This has burned me too. It would be nice if the errors were more
prominent, perhaps repeated at the end of the output?
Mike
While we are on the subject, is it possible to make it "die" when
incorrect (non-existent) options are passed to a context command? Is
there any way at all of knowing if the option did anything (even by
examining the log?)
No, this is not possible and even such a feature would increase
the compile time a lot, e.g. I used list with valid names in a earlier
version of my letter module and it was 30% slower than the current
version and now imagine what happens if you check each key in a
assignment list.
OK. It seems strange (coming from a programming background).
If it is only the compile time, then a command line switch might be an
option. (But it sounds like it is inherently hard to do, now).
i can probably implement some kind of checking (runtime switch, or maybe
even switch at format generation time) but i will do so only when i've
completely split of the mkiv code
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
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
