On Mon, 24 Aug 2009, Wolfgang Schuster wrote:
Am 24.08.2009 um 16:27 schrieb Aditya Mahajan:
To stop the TeX run we can have
\setupmodule[contextversion=2009.08.22]
at the begin of a module and ConTeXt will abort the run if the key
'contextversion' has a value and context is older than the user has
requested.
Do you want this to check to be part of the definition of \setupmodule?
One difficultly that I see is that typically this will mean that we need
to set this separately for each engine.
I don't need such a check, it was Olivers idea and I thought about a idea
how this
can be integrated without introducing a new command which breaks backward
compatibility.
I meant that when you said
\setupmodule[contextversion=...]", what is the implementation you had in
mind. \setupmodule macro doing the checking, or the module writer doing the
checking.
I think it's up to the developer to write something in the module,
e.g.
http://bitbucket.org/wolfs/simplefonts/src/46a1f454bccc/files/t-simplefonts.tex
but it's not so hard to integrate it into the \setupmodule command.
Thanks for clarifying. I also think that it is better to do this
selectively for each module rather than in the core.
Aditya
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
