From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec/context error messages [MkIV]
Date: Tue, 25 May 2010 08:40:47 +0200 [thread overview]
Message-ID: <4BFB70EF.2080107@elvenkind.com> (raw)
In-Reply-To: <20100525000022.GA8506@urvas>
Rogutės Sparnuotos wrote:
>
> One more question regarding error reporting: why are invalid parameters to
> commands _silently_ ignored?
For speed reasons. Checking the values would be a pretty slow process,
so you definitely don't want elaborate tests on a document that is known
to be ok.
There has been some thought about a special version of context that is
slow but does all these tests. Afaik, this has never materialized, I
suspect mainly because it is not always that easy to decide what is
valid and what is not (some commands delegate key-value parsing to
other commands, other commands are themselves generated on the fly).
For MkIV, there has been some work done by Luigi on figuring out what
commands are actually present, perhaps this can produce a basis to
look at a 'checked' context version again in the future.
Best wishes,
Taco
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-05-25 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 18:07 texexec/context error messages [MkIV] [vim] Rogutės Sparnuotos
2010-05-23 17:24 ` Aditya Mahajan
2010-05-25 0:00 ` texexec/context error messages [MkIV] Rogutės Sparnuotos
2010-05-25 6:40 ` Taco Hoekwater [this message]
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=4BFB70EF.2080107@elvenkind.com \
--to=taco@elvenkind.com \
--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).