in reply to Re: Parsing output from a 'system' call into objects?
in thread Parsing output from a 'system' call into objects?

For your information, most (if not all) of your print statements can be interpolated. So this:

print 'From hash'."\n"; 
for my $o (@order) { 
  my $h=$array->{$o}; 
  print ' ID = '.$h->{ID}."\n"; 
  print '  CoID  = '.$h->{CoID}."\n"; 
  print '  State = '.$h->{State}."\n";

[download]

Becomes this:

print "From hash\n"; 
for my $o (@order) { 
  my $h=$array->{$o}; 
  print "  ID    = $h->{ID}\n"; 
  print "  CoID  = $h->{CoID}\n"; 
  print "  State = $h->{State}\n";

[download]

Or:

print "From hash\n"; 
for my $o (@order) { 
  print "" .
        "  ID    = $array->{$o}->{ID}\n" .
        "  CoID  = $array->{$o}{CoID}\n" .
        "  State = $array->{$o}->{State}\n";

[download]

Or with a heredoc, but I digress.

Also, I'm curious as to why you're calling a hash $array... ;)

Replies are listed 'Best First'.
Re^3: Parsing output from a 'system' call into objects?
by huck (Prior) on Feb 21, 2017 at 20:31 UTC

    What no example this time to prove it? I thought you always wanted to see examples

    I prefer to make it clear when a value comes from a variable rather than infer it does via interpolation. It also means it is clearer when i say 

    my $thing='dog'; 
print 'many '.$thing.'s'."\n";

    [download]
    rather than the more obscure 
    my $thing='dog'; 
print "many ${thing}s\n";

    [download]
    without getting caught by 
    my $thing='dog'; 
print "many $things\n";

    [download]
    Being clear is a good habit i started about 4 decades ago, after trying to read other peoples APL code. I mostly say my $n=scalar(@array); for clarity too.

    You are right about calling it $array, it started because eval142 said he wanted an indexed array of objects.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom