Dahlke, Doug wrote: > I would usually agree, but the fact that it works in 2000 and not 98 > makes me suspect an operating system change as I'm sure the version of > perl is probably the same version, therefore should handle file paths > the same. Would be interesting to test out.
Two different shells. > -----Original Message----- > From: $Bill Luebkert [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 11, 2003 11:25 AM > To: [EMAIL PROTECTED] > Subject: Re: Another Dos question! > > > Dahlke, Doug wrote: > > >>My guess is that windows 2k is doing slash to backslash translation >>from the make of perl you have. Windows 98 doesn't apparently do >>that. I've > > > I'm not sure it's a 98 thingy. Most of the time you can use / in place > of \. The exception is when you shell out to a shell that only likes \. > Then you can do as below. I tend to do everything as / and then just > before the shell-out, I will do a s#/#\\#g on the exe path and possibly > on some args. > > >>seen where people have had to describe file paths like this to be >>compatible for both. >> >>$filename_winword="C:\\Program Files\\Microsoft >>Office\\Office\\WINWORD.EXE"; >> >>Two "\" are required as \ is a special character. Try this and see if > > >>that works. -- ,-/- __ _ _ $Bill Luebkert Mailto:[EMAIL PROTECTED] (_/ / ) // // DBE Collectibles Mailto:[EMAIL PROTECTED] / ) /--< o // // Castle of Medieval Myth & Magic http://www.todbe.com/ -/-' /___/_<_</_</_ http://dbecoll.tripod.com/ (My Perl/Lakers stuff) _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
