Re^2: Convert Shell script to Perl

exec does not behave in the same way on Windows and UNIX, so it might be better to use system instead, which is similar on both (although there are still a few differences).

Although the latest ksh93 versions exec on the last statement within a script, I don't think that bash does.

One other thing to be aware of, environment variables on UNIX are case sensitive but on Windows are not - that can catch you out.

Comment on Re^2: Convert Shell script to Perl

Replies are listed 'Best First'.
Re^3: Convert Shell script to Perl by akrrs7 (Acolyte) on Oct 10, 2011 at 15:26 UTC
This is the code: `use strict; use warnings; $ENV {'LIBDIR'}='$MY_XALANHOME/bin'; $ENV {'LOCALCLASSPATH'}='$ENV{LIBDIR}:/xalan.jar'; $ENV {'LOCALCLASSPATH'}='$ENV{LOCALCLASSPATH}:$ENV{LIBDIR}/xml-apis.ja +r'; $ENV {'LOCALCLASSPATH'}='$ENV{LOCALCLASSPATH}:$ENV{LIBDIR}/xercesImpl. +jar';` [download] When I run the perl program from the command line using - perl abc.pl - I don't get any error messages. When I run the following command from the commandline: `perl $ENV{'LIBDIR'}='C:\SOMEFOLDER';` [download] I get a message saying - can't open perl script "$ENV": no such file or directory. I would've expected to create a new environment variable called LIBDIR with the c:\somefolder as the value ? Thanks	[reply] [d/l] [select]
Re^4: Convert Shell script to Perl by Utilitarian (Vicar) on Oct 10, 2011 at 15:43 UTC
Two things, you need to tell the Perl interpreter to execute the code rather than look for a file of that name and the environment variables will not be set int the parent process (your shell) only in the Perl process and its children. So while `perl -e "$ENV{LIBDIR'}='C:\SOMEFOLDER';"` would create the varable, it would cease to exist when Perl exited. `print "Good ",qw(night morning afternoon evening)[(localtime)[2]/6]," fellow monks."`	[reply] [d/l] [select]