Doug McNutt wrote: > > I have a MacPerl script which uses no explicit library modules. Run as an > MPW tool it accepts a single command line argument which is the filename of > an output file. Runs fine. > > So I send it via e-mail to a colleague who is using ActivePerl build 515 in > which control is via an MSDOS window under Windoze98. > > I can enter a DOS command to execute the sample hello world script and it > runs OK. I can use perl -e "print time" and it works fine. When I give it > the command > > perl myscript.pl outputfile.txt > > I get absolutely nothing. -w doesn't help, -D seems to say that myscript > ended before it did anything. Changing the name of the script to a > nonexistant file generates a "can't find" message so I'm pretty sure perl is > attempting to run myscript.pl. There is no #! line in my script but then > there isn't one in the sample hello world script either. What about -c? > Very early in the script I do > > open OUTPUT ">".ARGV[0] or die "message"; Perhaps you need a dollar sign in that line? Copy and pasting the actual code is preferable to retyping it with errors. > I don't get the message. So... I'm off to the bookstore to learn perl for > Win32 (32 bit Windoze, not version 3.1) and I hate the thought. Has anyone > else faced my problem? I need a set of "Win32 perl for dummies" instructions > for me and my correspondent. > > -->From the USA, the only socialist country that refuses to admit it. > Why do you need to "learn perl for Win32"? If your script is properly platform independent, you shouldn't have to worry about it. The main difference between MacPerl and ActivePerl 515 is that MacPerl is based on perl5.004, and ActivePerl 515 is based on perl5.005_03. Without seeing the script, I can't say why it doesn't work. :) (How many lines of code is it?) Ronald ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org