Michael S. Robeson II wrote:
I came across some code on the internet that looks like this (this
is only part of the script):
while () {
$line=$_;
if ($line=~/^>(.+)/) {
if ($seq) {
$pro{$name}=$seq;
#print "SEQ:\n$pro\n\n";
}
Well yeah, the indentation makes it much more clearer. However, this
does not help me understand how the nested "if" statements are working.
Which of the two "if" statements gets evaluated first? I am trying to
figure out "in english" what the "if" statements are actually doing. Is
it saying:
On 7/2/2004 10:25 PM, Michael S. Robeson II wrote:
Well yeah, the indentation makes it much more clearer. However, this
does not help me understand how the nested "if" statements are working.
Which of the two "if" statements gets evaluated first? I am trying to
figure out "in english" what the "
On 7/3/2004 4:38 AM, Randy W. Sims wrote:
Tidied up a little more:
Actually, I'd probably invert the condition to make it clearer that it's
accumulating multi-line sequences.
my( %pro, @names);
my( $name, $seq, $k );
while (defined( my $line = )) {
unless ($line =~ /^>(.+)/) {
chomp(
Michael S. Robeson II wrote:
Which of the two "if" statements gets evaluated first? I am trying
to figure out "in english" what the "if" statements are actually
doing. Is it saying:
"If a line begins with ">bla-bla" and if $seq (which appears no
where else in the code other than " $seq="" ") ex
Ok, that make much more sense - I think. So, I guess, the outer 'if'
and 'else' statements get evaluated first. Then the inner 'if' can
proceed once all the lines of data were gathered in the outer 'else'
statement. This way the lines can be assigned as a key-value pair in
the hash. I guess the
No, your post was not in the last e-mail digest I received, unless I
missed it somehow? But the link you provided seems to clear things up
for me. So, it's not about the order of operation but the timing of
when the variables actually get defined.
That is, during the beginning of the loop since
Great, thanks for the help!
-Mike
On Jul 3, 2004, at 2:16 PM, Gunnar Hjalmarsson wrote:
Michael S. Robeson II wrote:
No, your post was not in the last e-mail digest I received,
I see. Sometimes I think that digest mode for mailing lists is a
nuisance. ;-)
But the link you provided seems to clear th
>> print "$tline[$i];
You are missing a quote on all 3 of these lines, it should be:
print "$tline[$i]";
But there is probably no reason to have a single variable in quotes
alone, so I recommend this:
print $tline[$i];
Rob
-Original Message-
From: Michael Simmons [mailto:[EMAIL P
Michael Simmons wrote:
>
> Does anyone see what the problem with this is?
>
> if ( $tline[$i] =~ /^$name\s/ ) {
> if ( $tline[$i] =~ /\scname\s/ ) {
> print "Found the following alias: \n";
> print "$tline[$i];
> }
> elsif ( $t
On 4/13/10 Tue Apr 13, 2010 4:35 PM, "Mimi Cafe"
scribbled:
> I think this will work, but is it elegant.?
Yes, it will work, and yes, it is elegant, as long as it encapsulates the
logic that is required by your program.
Be sure and watch your indenting, so you can mentally group the correct
b
> "JG" == Jim Gibson writes:
JG> On 4/13/10 Tue Apr 13, 2010 4:35 PM, "Mimi Cafe"
JG> scribbled:
>> I think this will work, but is it elegant.?
JG> Yes, it will work, and yes, it is elegant, as long as it encapsulates the
JG> logic that is required by your program.
i disagree
Hi;
On Tue, Apr 13, 2010 at 19:54, Uri Guttman wrote:
>> "JG" == Jim Gibson writes:
>
> JG> On 4/13/10 Tue Apr 13, 2010 4:35 PM, "Mimi Cafe"
>
> JG> scribbled:
>
> >> I think this will work, but is it elegant.?
>
> JG> Yes, it will work, and yes, it is elegant, as long as it encapsul
On Wednesday 14 Apr 2010 02:35:50 Mimi Cafe wrote:
> I think this will work, but is it elegant.?
>
>
>
> If (condition){
>
>if (nexted_condition){
>
> do this.
>
>}
>
>Elsif (nexted_condition){
>
> Do that...
>
>}
>
> else{
>
> Do something else.
>
>
[mailto:jimsgib...@gmail.com]
Sent: 14 April 2010 01:36
To: beginners@perl.org
Subject: Re: Nested if and elsif and else
On 4/13/10 Tue Apr 13, 2010 4:35 PM, "Mimi Cafe"
scribbled:
> I think this will work, but is it elegant.?
Yes, it will work, and yes, it is elegant, as long as it enc
On 2010.04.13 23:17, Kenneth Wolcott wrote:
> Hi;
>
> On Tue, Apr 13, 2010 at 19:54, Uri Guttman wrote:
>>> "JG" == Jim Gibson writes:
>>
>> JG> On 4/13/10 Tue Apr 13, 2010 4:35 PM, "Mimi Cafe"
>>
>> JG> scribbled:
>>
>> >> I think this will work, but is it elegant.?
>>
>> JG> Yes, i
Hi Mimi,
Mimi Cafe wrote:
I think this will work, but is it elegant.?
If (condition){
if (nexted_condition){
As others have noted, it will work. But as for elegance, this is a very subjective opinion and
contrary to what recent comments have said, my take on it is that it depends on
"Uri Guttman" writes:
> i disagree that it is elegant. too often if/else lists are not
> needed. many can be replaced by dispatch tables. if one of the clauses
> does just a return or next/last that can be replaced with a modifier or
> shorter statement. without ANY serious work, i have over 10k
Harry Putnam wrote:
> "Uri Guttman" writes:
>
>> i disagree that it is elegant. too often if/else lists
>> are not
>> needed. many can be replaced by dispatch tables. if one
>> of the clauses
>> does just a return or next/last that can be replaced
>> with a modifier or
>> shorter statement. withou
r...@i.frys.com writes:
> Here's an example I gave in a similar question in another
> forum.
Thanks...
I'm sorry to ask more but if someone asked to be shown an
if/elsif/else construct being replaced by a dispatch table, I don't
really see how that answered there question. It didn't for me.
W
On 4/15/10 Thu Apr 15, 2010 9:21 AM, "Harry Putnam"
scribbled:
> r...@i.frys.com writes:
>
>> Here's an example I gave in a similar question in another
>> forum.
>
> Thanks...
>
> I'm sorry to ask more but if someone asked to be shown an
> if/elsif/else construct being replaced by a dispatc
On Apr 15, 9:21 am, rea...@newsguy.com (Harry Putnam) wrote:
> r...@i.frys.com writes:
> > Here's an example I gave in a similar question in another
> > forum.
>
> Thanks...
>
> I'm sorry to ask more but if someone asked to be shown an
> if/elsif/else construct being replaced by a dispatch table, I
Ron Bergin writes:
> Sorry for not posting the if/elsif/else block, but to me that part
> appeared to be obvious, but I guess it wasn't.
Probably would have been for all but the densist I guess. Not the
first time I've been guilty of that.
> I see that Jim has posted the if/elsif/else part, so
23 matches
Mail list logo
