On Wednesday, June 5, 2002, at 05:18 , Ron Powell wrote:
>
>> %
>> % or which ever your KULT fave login world is, and then sort
>> % out which path thingies belong where - ala
>> %
>> %if( $ARCH == "sgi" ) then
>>
>> Ahhh! If/elseif trees! Ick!
>>
>
>
> See, a great place for a SWITCH sta
> %
> % or which ever your KULT fave login world is, and then sort
> % out which path thingies belong where - ala
> %
> % if( $ARCH == "sgi" ) then
>
> Ahhh! If/elseif trees! Ick!
>
See, a great place for a SWITCH statement (*snicker*)
/me runs away
Sorry, but should have been split on : as stated by drieux.
Wags ;)
-Original Message-
From: Wagner, David --- Senior Programmer Analyst --- WGO
Sent: Tuesday, June 04, 2002 15:13
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Parsing a path environment
split on the ; and you now have array with all the elements of your
environment.
Wags ;)
-Original Message-
From: James Kelty [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 04, 2002 14:58
To: [EMAIL PROTECTED]
Subject: Parsing a path environment...
Hello.
I am writing a quick
On Tuesday, June 4, 2002, at 04:58 , David T-G wrote:
volks,
the reason that the grass is moving around, is
not that there is an earthquake, merely that the elephants
are dancing the polka here - nothing serious
[..]
> % the fine person wanted something more on the order of
> %
> % my
drieux, et al --
...and then drieux said...
%
% On Tuesday, June 4, 2002, at 03:17 , David T-G wrote:
% [..]
% >
% >You should be able to split on colons...
% >
% > [zero] [5:16pm] ~> perl -e 'foreach $p \
% >(split (/:/,$ENV{PATH})){print "$p\n"}'
%
% first off my complements on the skan
On Tuesday, June 4, 2002, at 03:17 , David T-G wrote:
[..]
>
> You should be able to split on colons...
>
> [zero] [5:16pm] ~> perl -e 'foreach $p \
> (split (/:/,$ENV{PATH})){print "$p\n"}'
first off my complements on the skank - although you know and I know
the fine person wanted someth
James --
...and then James Kelty said...
%
% Hello.
Hello!
%
% I am writing a quick script in order to parse a users $PATH variable, but I
% hit upon a quandry.
%
% The PATH environment is one long string with element separated by a ":", no
% mystery there, but
% how would I look at each in
Hello.
I am writing a quick script in order to parse a users $PATH variable, but I
hit upon a quandry.
The PATH environment is one long string with element separated by a ":", no
mystery there, but
how would I look at each individual element? Normally I would use split on a
line by line basis, b
