07-26-2011
Holy crap that's a boneheaded mistake, thanks. How ever now I'm getting 'fi' unexpected.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Good morning - I have publication lists from 34 different faculty members. I need to end up with the numbers of publications in common across all 34 faculty.
I need to grep person1 (last name) in list2, person1 in list3, person1 in list 4, etc., then person2 in list3, person 2 in list4, etc.,... (2 Replies)
Discussion started by: Peggy White
2 Replies
2. Shell Programming and Scripting
I have to to read files simultaneously in two nested loops,but am getting error can anyone do the needful.
useridFile=userIds.txt
fname=kiran.txt
exec<$useridFile
while read line
do
echo "User IDs are..$line"
USER_ID=$line
REMOTE_DIR_LOCATION="/home/test/$USER_ID"
SOURCE_DIR=$USER_ID... (1 Reply)
Discussion started by: KiranKumarKarre
1 Replies
3. Shell Programming and Scripting
I need help getting over this bump on how nested for loops work in shell. Say i was comparing files in a directory in any other language my for loop would look like so
for(int i=0;to then end; i++)
for(int y = i+1; to the end; y++)
I can't seem to understand how i can translate that... (5 Replies)
Discussion started by: taiL
5 Replies
4. Shell Programming and Scripting
You can use one while inside another?
I made the following script (without really knowing if I can use two while) to get 3 numbers different from each other at random:
num1=$(( $RANDOM % 10 ))
num2=$num1
while
do
num2=$(( $RANDOM % 10 ))
done
num3=$num1
while
do
while
do... (1 Reply)
Discussion started by: ale.dle
1 Replies
5. UNIX for Dummies Questions & Answers
Hi experts,
I just want to know if there is a better solution to my nested while read loops below:
while read line; do
while read line2; do
while read line3; do
echo "$line $line2 $line3"
done < file3.txt
done < file2.txt
done < file1.txt >... (4 Replies)
Discussion started by: chstr_14
4 Replies
6. Shell Programming and Scripting
Greetings All,
The following script attempts to enumerate all users in all groups in the group file(GROUP) and echo the following information:
GROUP ---> USER
The script is as follows:
IFS=","
for GROUP in `ypcat -k group | cut -d" " -f1`
do
for USER in `ypcat -k group... (13 Replies)
Discussion started by: jacksolm
13 Replies
7. UNIX for Dummies Questions & Answers
It's been a while since I used csh formatting and I am having a little bit of trouble with a few things. Things seem so much easier to execute in Matlab, however I need to do this on the terminal because of the programs I am trying to interact with.
So here's what I want to do: I have a file... (0 Replies)
Discussion started by: katia
0 Replies
8. Shell Programming and Scripting
for server in $(echo `cat /tmp/ScanHosts_${USERSNAME}.TXT`)
do
for portnumber in $(echo `cat /tmp/ScanPorts_${USERSNAME}.TXT`)
do
#echo ${server} ${portnumber}
... (3 Replies)
Discussion started by: SkySmart
3 Replies
9. Shell Programming and Scripting
Hello, I pulled out some old code from an unfinished project the other day and wanted to stream line it better. I know anything beyond a double loop is usually bad practice, and I came up with some logic for later that would no longer require the first loop in the following code that works:
... (5 Replies)
Discussion started by: Azrael
5 Replies
LEARN ABOUT DEBIAN
io::handle::prototype::fallback
IO::Handle::Prototype::Fallback(3pm) User Contributed Perl Documentation IO::Handle::Prototype::Fallback(3pm)
NAME
IO::Handle::Prototype::Fallback - Create IO::Handle like objects using a set of callbacks.
SYNOPSIS
my $fh = IO::Handle::Prototype::Fallback->new(
getline => sub {
my $fh = shift;
...
},
);
DESCRIPTION
This class provides a way to define a filehandle based on callbacks.
Fallback implementations are provided to the extent possible based on the provided callbacks, for both writing and reading.
SPECIAL CALLBACKS
This class provides two additional methods on top of IO::Handle, designed to let you implement things with a minimal amount of baggage.
The fallback methods are all best implemented using these, though these can be implemented in terms of Perl's standard methods too.
However, to provide the most consistent semantics, it's better to do this:
IO::Handle::Prototype::Fallback->new(
__read => sub {
shift @array;
},
);
Than this:
IO::Handle::Prototype::Fallback->new(
getline => sub {
shift @array;
},
);
Because the fallback implementation of "getline" implements all of the extra crap you'd need to handle to have a fully featured
implementation.
__read
Return a chunk of data of any size (could use $/ or not, it depends on you, unlike "getline" which probably should respect the value of
$/).
This avoids the annoying "substr" stuff you need to do with "read".
__write $string
Write out a string.
This is like a simplified "print", which can disregard $, and "$" as well as multiple argument forms, and does not have the extra
"substr" annoyance of "write" or "syswrite".
WRAPPING
If you provide a single reading related callback ("__read", "getline" or "read") then your callback will be used to implement all of the
other reading primitives using a string buffer.
These implementations handle $/ in all forms ("undef", ref to number and string), all the funny calling conventions for "read", etc.
FALLBACKS
Any callback that can be defined purely in terms of other callbacks in a way will be added. For instance "getc" can be implemented in terms
of "read", "say" can be implemented in terms of "print", "print" can be implemented in terms of "write", "write" can be implemented in
terms of "print", etc.
None of these require special wrapping and will always be added if their dependencies are present.
GLOB OVERLOADING
When overloaded as a glob a tied handle will be returned. This allows you to use the handle in Perl's IO builtins. For instance:
my $line = <$fh>
will not call the "getline" method natively, but the tied interface arranges for that to happen.
perl v5.10.1 2009-09-29 IO::Handle::Prototype::Fallback(3pm)