Re^2: Flat file handling

Or even better.... something like:

    my $xx = $Variable+($Component_number*$Variable);

      $Command = join(' ', 
              'EXEC', 
              $SPROC, 
              join(', ', 
               @CHOICE[1 .. $xx]).';';
[download]

This gives me an error though.

syntax error at 20_October_2004_H.pl line 143, near "';';"
Execution of 20_October_2004_H.pl aborted due to compilation errors.
[download]

I ended up not including $CHOICE[0] due to trial and error. Not sure why ... as you say ... it is a mess.

Comment on Re^2: Flat file handling Select or Download Code

Replies are listed 'Best First'.
Re^3: Flat file handling by davido (Cardinal) on Nov 18, 2004 at 17:58 UTC
You've got to clean it up a bit before it'll begin to make sense. Consider using a uniform practice of indentation. That will help in lining up brackets and parens, etc. Also, that whole schpiel where you've got `my $a.... my $b.... my $c....` [download] ...and so on... that's not doing anything for you. You're declaring those variables within a narrow lexical scope, and they're passing out of scope before you ever use them. That's pointless. And even if it were, shouldn't that be an array of 26 elements rather than 26 named variables? ...and maybe a loop? Anytime you find yourself writing something 26 times, it's time to use a loop. And even then, shouldn't those variable names have some meaning so a casual reader will know what they're for? The fact that they don't have meaningful names is probably why they've ended up not getting used anywhere else. As for why your followup snippet doesn't work, it's missing a closing paren, which you could identify more easily if you were to adopt a uniform indentation practice. Just some tips. I have no idea what the actual bug is, but there are underlying clarity problems that contribute to making it difficult for this piece of code to be developed, maintained, and understood. Dave	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Flat file handling
by davido (Cardinal) on Nov 18, 2004 at 17:58 UTC

You've got to clean it up a bit before it'll begin to make sense. Consider using a uniform practice of indentation. That will help in lining up brackets and parens, etc.

Also, that whole schpiel where you've got

my $a....
my $b....
my $c....
[download]

...and so on... that's not doing anything for you. You're declaring those variables within a narrow lexical scope, and they're passing out of scope before you ever use them. That's pointless. And even if it were, shouldn't that be an array of 26 elements rather than 26 named variables? ...and maybe a loop? Anytime you find yourself writing something 26 times, it's time to use a loop.

And even then, shouldn't those variable names have some meaning so a casual reader will know what they're for? The fact that they don't have meaningful names is probably why they've ended up not getting used anywhere else.

As for why your followup snippet doesn't work, it's missing a closing paren, which you could identify more easily if you were to adopt a uniform indentation practice.

Just some tips. I have no idea what the actual bug is, but there are underlying clarity problems that contribute to making it difficult for this piece of code to be developed, maintained, and understood.

Dave

[reply]
[d/l]