[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Hooks and Perl on Windows

From: Jason Butlin <roguejay_at_hotmail.com>
Date: 2004-11-24 08:49:09 CET

>From: Toby Johnson <toby@etjohnson.us>
>Reply-To: users@subversion.tigris.org
>To: Jason Butlin <roguejay@hotmail.com>
>CC: users@subversion.tigris.org
>Subject: Re: Hooks and Perl on Windows
>Date: Tue, 23 Nov 2004 14:14:33 -0500
>
>Jason Butlin wrote:
>
>>Interesting point about not calling exit, which is what I do - and seems
>>to work O.K. I might change it anyway.
>
>If called from another process, "exit" should be fine. But if you call a
>batch script with an "exit" in it from the command line (which you might do
>while testing), it will exit the command line instead of simply exiting the
>script. I didn't know about the /B switch that another poster mentioned
>however, so that should accomplish what you want instead of using my
>"trick".
>
>>My problem lies in the fact that after calling the Perl scrip %errorlevel%
>>will ALWAYS be equal to 0, no matter what the Perl script exits with. But
>>if I run the batch file from the command line, the after the Perl script
>>the errorlevel is correctly 0 or 1.
>
>Then there is a problem with the way you are calling your Perl script. Be
>sure to store %errorlevel% immediately after you execute it, or it might
>get overwritten by the next command.

Doh. External moving part error. Thanks to both replies - I needed to
perform some certain tasks regardless of the whether the Perl script failed
or not, so I did those before checking the errorlevel. Stupid mistake - but
we're all entitled to a few.

Thanks
Jay

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 24 08:52:15 2004

This is an archived mail posted to the Subversion Users mailing list.