ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: die if a module is missing
Date: Thu, 12 Mar 2009 11:38:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.0903121131210.3377@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <87iqmeepil.fsf@cordelia.devereux.me.uk>

On Thu, 12 Mar 2009, John Devereux wrote:

> Wolfgang Schuster <schuster.wolfgang@googlemail.com> writes:
>
>> Am 12.03.2009 um 15:06 schrieb John Devereux:
>>
>>> Michael Bynum <mdbynum@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).

TeX is no ordinary language. Currently, all keys that you pass are simply 
stored as macros. When a particular option is needed, ConTeXt checks the 
value of the corresponding macro, and decides what to do.

If you want to check the keys, you need that while storing the options as 
macros. This means an extra check for each value for each ConTeXt command. 
Since ConTeXt uses an extensive key-value configuration system, this means 
a lot of extra time. The same argument holds for stripping white spaces 
from key-value pairs. You can use \setupsomething[key=value] but not 
\setupsomething[ key = value ].

For module and environments, this problem can be solved by using

\unprotect
...

\setupsomething[\c!key=\v!value]

...

\protect

> 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).

Perhaps with luatex there may be an easier solution. But that would mean 
rewriting how options are handled internally --- a big and error-prone 
task.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-03-12 15:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 10:13 Jesse Alama
2009-03-12 13:59 ` Michael Bynum
2009-03-12 14:06   ` John Devereux
2009-03-12 14:19     ` Wolfgang Schuster
2009-03-12 15:20       ` John Devereux
2009-03-12 15:38         ` Aditya Mahajan [this message]
2009-03-12 15:38         ` Wolfgang Schuster
2009-03-13  8:38         ` Hans Hagen
2009-03-13  9:14           ` John Devereux
2009-03-13  9:31             ` Hans Hagen
2009-03-13 10:35               ` John Devereux
2009-03-12 14:21   ` Wolfgang Schuster
2009-03-14 19:05   ` Hans Hagen
2009-03-14 19:13     ` Aditya Mahajan
2009-03-14 19:21       ` Hans Hagen
2009-03-15 16:23       ` Hans Hagen
2009-03-16 12:14         ` Wolfgang Schuster
2009-03-16 13:27           ` Hans Hagen
2009-03-13 10:23 ` Mojca Miklavec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.00.0903121131210.3377@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).