[dev-context] texexec and return codes ... bad

Hans Hagen pragma at wxs.nl
Wed Jan 10 11:20:03 CET 2007

Taco Hoekwater wrote:
> Norbert Preining wrote:
>> On Die, 09 Jan 2007, Hans Hagen wrote:
>>> fixed in the beta already, i'll make a new current zip (has to do 
>>> with changes in pdftex) 
>> One question: I tested the release 2007-01-09 and the xetex bug is gone,
>> but the return value of texexec still is 0, even when aleph breaks
>> making a cont-en format. Does this mean that the beta version you are
>> talking about is *not* the 2007-01-09 release, but the next release?
> Hans, the same problem occurs in texsync, and I assume anything that
> is started by texmfstart.
> I do not know what the proper ruby syntax is for perl's exit(), but
> in general, you should return "zero" for success, anything else for
> failure (normally programs use simply "one" in all cases).
> If you do not call exit() yourself and do not call die() either
> (whatever the ruby equivalent of that is), the default return value
> is zero == success. That can be an enormous pain in the butt when
> texexec etc. are used inside scripts|makefiles.
ok, i found out there i already implemented some sort of error reporting and exit stuff but not for formats; i'll make a new zip (and keep my fingers crossed) 


                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl

More information about the dev-context mailing list