Isnt this a simple case of else if ? Loop would be better of course if i runs from 1 to 13, but for checking specific columns it may be better to use else if .
Yes, if...
If we knew what was really wanted we could all make better suggestions. When we're just given a pattern of three consecutive fields being checked and a statement that 13 fields will be checked, we have to guess at what should be done. With consecutive fields, a loop is probably better; with non-consecutive fields an if-else ladder or a loop over an array listing the fields to be tested will be needed. If the 13 field numbers are fixed but not consecutive, an if-else ladder will be faster. If the fields to be tested vary from invocation to invocation, creating an array of fields to be evaluated is a lot easier to set up the code in a BEGIN clause from command line or file input than rewriting an if-else ladder on the fly.
That is why threads are much shorter and suggestions are much better and usually arrive quicker when the requirements are carefully and clearly specified in the 1st post in a thread.
Hello,
Can you explain why in the first 2 commands the awk does not print anything? Is it looking of a specific format ?
Thanks.
$ echo 12a3 | awk '($1>=2) {print $1}' # prints nothing
$ echo 123a | awk '($1>=2) {print $1}' # prints nothing
$ echo a123 | awk '($1>=2) {print $1}'
a123... (1 Reply)
I do not know how to do this unless I use a bunch of if statements. I need a script to replace numbers in each record in a file. I am really getting tangled in this web.
If a fieldA (19 positions) is greater than 14 digits, I have to change the data (resulting fieldA is fixed 19 postions).
If... (5 Replies)
how can i specify more than 1 consition in the following AWK statament??
i.e. if $2 is ABCD and $3 is MNOP and $4 is KLPM
similarly for OR
#!/bin/ksh
awk -F '' ' $2 == "ABCD" { print $2, $3;}' file.xml (2 Replies)
Hi Everyone,
# cat 1
1;2;3;4;5;6
1;2;3;4;5;
# awk -F ";" '$5 == "5"' 1
1;2;3;4;5;6
1;2;3;4;5;
but the output is should be just "1;2;3;4;5;6" means 1st condition: $5 is 5; 2nd condition: $6 is not empty, please advice. Thanks (2 Replies)
Hi there,
I wanna define a variable 'tempbase'. Therefore I read a text file "base.out". "base.out" contains a list with four columns. 'tempbase' is the 4th entry in the line, where the first entry is equal to the predefined variable $orb1 and the second entry is equal to $orb2. I wrote the code... (2 Replies)
Hi there, here is my command
ssh host.local "/path/to/my/perscript/hostconfig.pl -s $HOST -d |awk '{if (\$4 > 120)print \"My error message\";exit}{s=0; for (i=1; i<=NF; i++) s++; if(s == 13) print \$3}'"
The problem is if conditional 1 is met (i.e $4 > 120), i don't see "My error message", the... (5 Replies)
Hi All,
I have a file with below contents.
"en2"/10.185.81.0:cluster_interconnect,"en5"/10.185.81.0:cluster_interconnect,"en6"/169.181.146.0:public
I want to take the interface name from the file and convert it as ipaddress using ifconfig command get the output like below
en6 ->... (2 Replies)
I'm having a problem pulling UID's from data. The data outputs a user's UID in one of three ways:
1. Error User user_name already assigned with <UID>
2. Success <UID> reserved for user_name
3. <a load of crap because there was a db failure yet somehow the UID is still in there>
I typically... (5 Replies)
Hello Friends,
I need to find some CDRs in production servers whose 1st field value and 2nd field value = 1 and 11th looks like 45.123... where there are more than 3 digits after comma.so i wrote a one liner, something like below but does not work, however when i used first and second conditions... (8 Replies)
fields(3pm) Perl Programmers Reference Guide fields(3pm)NAME
fields - compile-time class fields
SYNOPSIS
{
package Foo;
use fields qw(foo bar _Foo_private);
sub new {
my Foo $self = shift;
unless (ref $self) {
$self = fields::new($self);
$self->{_Foo_private} = "this is Foo's secret";
}
$self->{foo} = 10;
$self->{bar} = 20;
return $self;
}
}
my Foo $var = Foo::->new;
$var->{foo} = 42;
# this will generate a compile-time error
$var->{zap} = 42;
# subclassing
{
package Bar;
use base 'Foo';
use fields qw(baz _Bar_private); # not shared with Foo
sub new {
my $class = shift;
my $self = fields::new($class);
$self->SUPER::new(); # init base fields
$self->{baz} = 10; # init own fields
$self->{_Bar_private} = "this is Bar's secret";
return $self;
}
}
DESCRIPTION
The "fields" pragma enables compile-time verified class fields.
NOTE: The current implementation keeps the declared fields in the %FIELDS hash of the calling package, but this may change in future ver-
sions. Do not update the %FIELDS hash directly, because it must be created at compile-time for it to be fully useful, as is done by this
pragma.
If a typed lexical variable holding a reference is used to access a hash element and a package with the same name as the type has declared
class fields using this pragma, then the operation is turned into an array access at compile time.
The related "base" pragma will combine fields from base classes and any fields declared using the "fields" pragma. This enables field
inheritance to work properly.
Field names that start with an underscore character are made private to the class and are not visible to subclasses. Inherited fields can
be overridden but will generate a warning if used together with the "-w" switch.
The effect of all this is that you can have objects with named fields which are as compact and as fast arrays to access. This only works
as long as the objects are accessed through properly typed variables. If the objects are not typed, access is only checked at run time.
The following functions are supported:
new fields::new() creates and blesses a pseudo-hash comprised of the fields declared using the "fields" pragma into the specified
class. This makes it possible to write a constructor like this:
package Critter::Sounds;
use fields qw(cat dog bird);
sub new {
my Critter::Sounds $self = shift;
$self = fields::new($self) unless ref $self;
$self->{cat} = 'meow'; # scalar element
@$self{'dog','bird'} = ('bark','tweet'); # slice
return $self;
}
phash fields::phash() can be used to create and initialize a plain (unblessed) pseudo-hash. This function should always be used instead
of creating pseudo-hashes directly.
If the first argument is a reference to an array, the pseudo-hash will be created with keys from that array. If a second argument
is supplied, it must also be a reference to an array whose elements will be used as the values. If the second array contains less
elements than the first, the trailing elements of the pseudo-hash will not be initialized. This makes it particularly useful for
creating a pseudo-hash from subroutine arguments:
sub dogtag {
my $tag = fields::phash([qw(name rank ser_num)], [@_]);
}
fields::phash() also accepts a list of key-value pairs that will be used to construct the pseudo hash. Examples:
my $tag = fields::phash(name => "Joe",
rank => "captain",
ser_num => 42);
my $pseudohash = fields::phash(%args);
SEE ALSO
base, "Pseudo-hashes: Using an array as a hash" in perlref
perl v5.8.0 2002-06-01 fields(3pm)