> Actually, being technical about this and looking at your OP there is no > question there at all! Search for it. Look for a question mark. There is > none. There is merely the sentence "Please advise" and that's what you got!
Congratulations! I was wondering when someone would point that out; and for the record, "?". > "I can't use this pair of pliers to tow this boat. Please advise". - > Well how about cha use a tow instead? Clever. >> Seeing as how you don't know what common tasks I am trying to >> automate, I don't see how you can presume to know the scripts do not >> have to be written in a Windows specific way. >It's pretty much a given unless you simply insist on doing it in a >Windows specific way. My operating system is Windows and therefore many of my applications are only compatible with Windows. In order to interact with the application through their SDKs, I need to use Win32 modules. > I gave you an answer for your "short term solution". If you insist on > using a Windows oriented product such as ActiveState then fire up cmd > and type in Windows specific path names to your Windows only ActiveState > Perl scripts. Where's the problem? I'm lazy, it's inconvenient. >> Executing a script That appears in my $PATH will automatically expand >> using cygwin style pathing. > This statement doesn't even make sense. What exactly is expanding? If > you type myscript.pl 'C:\\Cygwin\\tmp\\file' and myscript.pl echoes out > the first arg what do *you* get? That example I can simply handle in the application, but I mean more when I invoke the script. When it is in my $PATH and I type myscript.pl, the full path is expanded and passed to the interpreter with cygwin style paths. -- 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/
