in reply to Re^4: Iterating Through Cell Blocks with Spreadsheet::Read
in thread Iterating Through Cell Blocks with Spreadsheet::Read

Yes indeed, chexmix, recommended change was made on all affected lines. Here's the revised test script:
use Spreadsheet::Read; my $inbook = "Data_File.xlsx"; $book = ReadData ($inbook); my @x = qw(F G H I J K); for my $sheet_index (1 .. $sheet_count) { my $sheet = $book->[$sheet_index] or next; foreach (@x) { $name = $sheet{"${_}28"}; $strain = $sheet{"${_}29"}; $initdensity = $sheet{"${_}30"}; $finaldensity = $sheet{"${_}31"}; $avedensity = $sheet{"${_}32"}; print "Found sheet with label: $sheet{label}\n"; print "COL=$_ $name $strain $initdensity $finaldensity $avedens +ity\n"; } }
Hopefully it helps you see my error. Regards, Hammer

Replies are listed 'Best First'.
Re^6: Iterating Through Cell Blocks with Spreadsheet::Read
by AnomalousMonk (Archbishop) on Oct 08, 2013 at 19:55 UTC
    [from Re^2: Iterating Through Cell Blocks with Spreadsheet::Read:]
    I still get the same error "Use of uninitialized value in concatenation (.) or string at..." on the print statement after replacing lines like "$name = $sheet{"$_28"}" with "$name = $sheet{"${_}28"}".

    I'm assuming the error message quoted from an earlier reply refers to the code most recently posted. In this code, my interpretation of the
        my $sheet = $book->[$sheet_index] or next;
    statement is that it creates a hash reference named $sheet. If you dump this variable with something like
        print Dumper $sheet;
    is that what you see? If the scalar  $sheet is a hash reference, its elements are accessed like  $sheet->{'string'} (note the  -> operator; see The Arrow Operator in perlop; also see perlref).

    After that, statements like
        $name = $sheet{"${_}28"};
    assign values of keys of the hash named  %sheet (not the hash reference  $sheet) to variables. Does this hash exist? It is not shown in your posted code, and I don't understand how your code can possibly work if it does not exist. Are you aware of the phenomenon of "autovivification" in Perl?

    Do you have warnings and strictures (see warnings and strict) enabled, i.e., do you have statements like
        use warnings;
        use strict;
    at or very near the top of each source file? Bugs arising from autovivification direct-versus-referential access confusion can easily bite without warnings and strictures.

    Update: On second thought, the reference to autovivification above is misguided, but the hash  %sheet really does have to exist somewhere with meaningful data in it for the posted code to work.

      Anomalous, thanks for your response. Adding a line "print Dumper $sheet;" generates error:
      print() on unopened filehandle Dumper at ./ line 33.
      References like:
      my $sheet_count = $book->[0]{sheets};
      before the loop work, but even though I have:
      $sheet = $book->[$sheet_index] or next;
      this does not seem to be doing the trick. I have tried many variations with no success. I had know autovivification as Perl magic. Knowing the proper term allows me to read about the full effects of the feature. Thanks for that. Adding:
      use warnings; use strict;
      up top makes no difference in the result. Thanks, Hammer.

        You need to
            use Data::Dumper;
        in order for the  Dumper function to be accessible in your code; then
            print Dumper $sheet;
        will actually print something. See Data::Dumper. (I tend to like Data::Dump a bit better.)

        ... even though I have:
        $sheet = $book->[$sheet_index] or next;
        this does not seem to be doing the trick.

        But my point remains the same: in order for a statement like
            $name = $sheet{"${_}28"};
        to work, a hash named  %sheet must exist somewhere in your code (somewhere in scope, that is). I.e., there must be a statement something like
            my %sheet = ( ... );
        somewhere. Do you say that such a statement exists?

        Update: The other point to make is that if the  %sheet hash actually does exist, the expressions  $sheet{"F28"} and  $sheet->{"F28"} access two completely different hashes!