Keep in mind though that this might happen frequently without
warning since you're working with development code here. For the
moment I'm merely trying to establish something along the lines of
a nightly installer build ... since there's no regression test
suite I can't even test whether anything works but the most basic
features. Also, modules don't check for a minimum kernel version
required :-(
There is a command to check the context version
%D \macros
%D {doifolderversionelse}
%D
%D We start with a macro specially for Aditya who wants to be able
%D to use development versions of \MKIV\ for real documents.
%D
%D \starttyping
%D \doifolderversionelse\contextversion{2001.02.03}{yes}{no}
%D \doifolderversionelse\contextversion{3001.02.03}{yes}{no}
%D \stoptyping
and end the module and output a message in the terminal but then you
will
you will get a error message in the document itself because a few
commands
(e.g. \setmainfont) are no longer defined.
Would it then be possible to have ConTeXt grind to a complete halt
once it encounters a module whose minimum requirements aren't met?
Since TeX would have to give up on the document anyway perhaps an
early bail out could be the more graceful option ... what do you think?
Oliver
_______________________________________________
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
