Re^2: ParseExcel Again

Its normal code to parse .xls

$excelRowCounter=0;
my $parser = Spreadsheet::ParseExcel->new(
                                      CellHandler => \&excelCellhandle
+r,
                                      NotSetCell  => 1,
                                      Parameters => "XXXXXXXXX"
                            );

$parser->parse($currentFile);

sub excelCellhandler
{
    # my $workbook    = $_[0];
    # my $sheet_index = $_[1];
    my $row         = $_[2];
    # my $col         = $_[3];
    my $cell        = $_[4];
    my $q;
    

    if($excelRowCounter == $row)
    {
    $q = $cell->unformatted();
    $text .= $v;     
        
    }
    else
    {
    if(length($text) > 2097152)
    {
    do something          
    
    return 
    }
    $excelRowCounter = $row;
    
    $q = $cell->unformatted();
     $text .= $v;      
        
    }
}
[download]

Comment on Re^2: ParseExcel Again Download Code

Replies are listed 'Best First'.
Re^3: ParseExcel Again by tmharish (Friar) on Feb 13, 2013 at 11:20 UTC
If you are not happy with a CPAN module you will have to essentially re-write it ( or at least parts of it ) You can get the code from CPAN or GitHub, find the chunks that you are using ( which might be a pain considering the number of sub-modules it has ) and then try to optimize it. Also that module does not look like it has been maintained in over two years, but you could try to get in touch with the maintainers. If you do manage to speed it up / improve it, you might want to submit a patch. Or you could just try and get the same data in CSV - is that possible?	[reply]
Re^4: ParseExcel Again by Anonymous Monk on Feb 13, 2013 at 11:36 UTC
CSV is not an option. The module has so many dependecies that speeding it up or identifying functions which i dont require is very difficult	[reply]
Re^5: ParseExcel Again by marto (Cardinal) on Feb 13, 2013 at 11:46 UTC
"speeding it up or identifying functions which i dont require is very difficult" Consider profiling your code. Devel::NYTProf, this includes documentation/screen casts explaining how to use the module to locate problems and areas for optimization. See also Debugging and Optimization. Alternatively, invest in a system with more RAM, faster disks (SSD) and a better CPU.	[reply]
Re^5: ParseExcel Again by ww (Archbishop) on Feb 13, 2013 at 12:09 UTC
I suspect that what tmharish was suggesting was that you save your problematic spreadsheet as CSV or TSV (doing so uses an excel function so no new dependancies there) and then use a CSV module -- such as `Parse-CSV 2.00` -- to extract the data you're looking for. If you didn't program your executable by toggling in binary, it wasn't really programming!	[reply]