Re^2: Comandline arguements when perl code is getting executed from command line

#!/usr/bin/ksh

cat file | while read i
do
 file_name=`echo $i | awk -F"|" '{print $1}'` #get the file_name
 export type=`echo $i | awk -F"|" '{print $2}'` #get the customer type
+ setting for the file
 perl -nle '/TABLE/ && print "$ARGV:$_:@ARGV"' $file_name $type
done
[download]

thanks a lot, the above too worked fine as expected.

Comment on Re^2: Comandline arguements when perl code is getting executed from command line Download Code

Replies are listed 'Best First'.
Re^3: Comandline arguements when perl code is getting executed from command line by sgt (Deacon) on Jan 16, 2007 at 10:44 UTC
hi, don't you have a shell that supports $(...) to avoid backquotes `...`; the first does nest properly and the second does not. Modern shell hackers consider the second form obsolete, but yes it is portable and is probably the way to go if you do configure-like sport... cheers --stephan	[reply]
Re^3: Comandline arguements when perl code is getting executed from command line by ikegami (Patriarch) on Jan 16, 2007 at 15:46 UTC
Not really. `-n` tries to open the value of $type as a file. By the way, won't you have a problem if $file_name or $type contains shell metacharacters?	[reply] [d/l]