This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: More error level issues
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: "AVT-Wien" <wien at avt dot at>, <cygwin at cygwin dot com>
- Date: Thu, 31 Mar 2005 15:09:01 -0500
- Subject: Re: More error level issues
- References: <NDBBLEGOCELADMPKABOKAEAEFLAB.wien@avt.at>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 01:48 PM 3/31/2005, you wrote:
>Hi,
>
>With cygwin1.dll version 1.5.13 exit codes to Windows (I use W2K and XP) have
>changed by a factor of 256 (shift of 8 bits) as mentioned in the 2 messages
>cited below. I have processes running under Windows shells that run several
>days, doing a lot of steps (both unix tools like gawk, head, sort etc. and gcc
>compiled c-programs) fully automatically. Flow control heavily relies on return
>codes (%errorlevel% in Windows). The codes were introduced according to the
>exit codes of the previous versions of the cygwin-libraries that put into
>%errorlevel% exactly what was provided by exit(). With the upgrade to 1.5.13
>the exit codes changed by a factor of 256, and since Windows XP uses 16 bit
>codes, are now limited to a maximum value of 255.
>
>Before I check and change many hundreds of lines of *.bat files: Will this
>return code behaviour change again in the future or can I assume this will
>last?
Current snapshots have the following change applied:
- Right shift exit code by eight when not started in a cygwin environment
If you want to see if this helps in your situation, try a recent snapshot
(<http://cygwin.com/snapshots/>).
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/