Am Dienstag, 25. November 2003 21:45 schrieb kfogel@collab.net:
> Jani Averbach <jaa@jaa.iki.fi> writes:
> > > "It's difficult, *from a .BAT or other script*, to invoke a
> > > program in the background."
> >
> > John Peacock wrote:
> > http://www.contactor.se/~dast/svnusers/archive-2003-11/0555.shtml
>
> Ah, yes -- thanks, I'd forgotten about that!
>
> Do we know that this solution is portable across all/most Win* systems?
That works with the NT-series of windows.
And even there *I* wouldn't want to do that:
I use perl often, and on win32 it's activestate's.
I tried to do a
`start cmd.exe /c ...`
or
system("start cmd.exe /c ...")
from inside perl, as there's no fork() in windows, and system() waits.
But: that doesn't work, as perl (in this case) waits for the parent shell to
abort, which doesn't, as members of this process group are still running
(or some other problem like this - I didn't investigate further)
My solution was to use a 4-liner in C:
int main(int argc, char *args[])
{
WinExec(args[1], SW_SHOW);
}
(or, to be honest, the WinMain()-variant - and this is from memory, I'm not
sure about the parameters. BTW, I use SW_HIDE to hide the resulting window,
as a dos-box is not very pretty)
Now if that problem occurs will depend on the exact calling variant - but it
may still happen!
So be warned ....
(BTW, did I say that I'm all for using a property in the repository to tell
the fs layer whether to deltify immediately?? :-)
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 26 07:15:47 2003