You *could* have the perl script set all of the environment
variables, then exec a new shell.
___
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
At 09:51 AM 1/16/2003 -0500, [EMAIL PROTECTED] wrote:
Hanes, Philipp wrote:
Probably not.
Hi Philipp, how're things?
That's a bummer.
TMTOWTDI becomes NCD - No Can Do
If it is any consolation, it isn't Perl's fault. It is inherent in the
nature of parent/child processes. The child
On Thu, Jan 16, 2003 at 09:59:52AM -0500, Ron Newman wrote:
You *could* have the perl script set all of the environment
variables, then exec a new shell.
Abigail came up with quite a neat move involving a double exec written
up on Fun With Perl list. In hir own words,
From: abigail[at]foad.org
Unix folks are used to these limitations on how you can use
environment variables. Do things work the same way in Windows?
___
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Charles Reitzel [EMAIL PROTECTED] writes:
[snip]
BEGIN
{
$HomeDir = '/usr/local/foo';
$Foo = 'foo';
@Bar = ( qw(Foo Baz Bar) );
%Baz = { Foo = $Foo, Bar = \@Bar };
}
[snip]
The %Baz is
