On Sun, 23 Aug 2009, Wolfgang Schuster wrote:
Am 22.08.2009 um 13:47 schrieb Oliver Buerschaper:
What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-)
*You* want to write a test suite for ConTeXt?
The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See http://wiki.contextgarden.net/Test
Perhaps one could even integrate this requirement check into the module loading code of the kernel. For example, one might enforce that each valid module has to declare a field like "minkernelversion" in its header ... just thinking out loud.
The problem with such systems is they lead always to incompatibilities with ConTeXt installations (think about TeXLive) and we had one at the end of last year when Hans changed the multilingual interface to allow a persian interface.
Loading of lua files has this feature. For modules, asking for a minimum kernel version is no guarantee that the module will work with future versions of ConTeXT :-) Aditya