Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Spreadsheet-ParseExcel CPAN distribution.

Maintainer(s)' notes

If you are reporting a bug in Spreadsheet::ParseExcel here are some pointers

1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.

2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.

    #!/usr/bin/perl -w

    print "\n    Perl version   : $]";
    print "\n    OS name        : $^O";
    print "\n    Module versions: (not all are required)\n";

    my @modules = qw(
                      Spreadsheet::ParseExcel
                      Scalar::Util
                      Unicode::Map
                      Spreadsheet::WriteExcel
                      Parse::RecDescent
                      File::Temp
                      OLE::Storage_Lite
                      IO::Stringy
                    );

    for my $module (@modules) {
        my $version;
        eval "require $module";

        if (not $@) {
            $version = $module->VERSION;
            $version = '(unknown)' if not defined $version;
        }
        else {
            $version = '(not installed)';
        }

        printf "%21s%-24s\t%s\n", "", $module, $version;
    }

    __END__

3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.

4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.

5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org

6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.

7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.

Asking a question

If you would like to ask a more general question there is the Spreadsheet::ParseExcel Google Group.

Report information
The Basics
Id: 47905
Status: resolved
Priority: 0/
Queue: Spreadsheet-ParseExcel

People
Owner: Nobody in particular
Requestors: Dave.Kubasiak [...] Enerwise.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Use of uninitialized value in length
Date: Wed, 15 Jul 2009 08:29:30 -0400
To: <bug-Spreadsheet-ParseExcel [...] rt.cpan.org>
From: "Kubasiak, Dave" <Dave.Kubasiak [...] Enerwise.com>
Download XLtester.pl
text/x-perl 205b

Message body is not shown because sender requested not to inline it.

Download test.xls
application/vnd.ms-excel 21k

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 1.9k
I have a script that reads Excel files that *was* working using Spreadsheet::ParseExcel 0.44. When I grabbed the latest version (0.49), my script stopped working and throws the following error: Use of uninitialized value in length at C:/Perl/site/lib/Spreadsheet/ParseExcel/Utility.pm line 974. Here is my system info (I use ActiveState Perl): Perl version : 5.008008 OS name : MSWin32 Module versions: (not all are required) Spreadsheet::ParseExcel 0.49 Scalar::Util 1.18 Unicode::Map 0.112 Spreadsheet::WriteExcel 2.17 Parse::RecDescent 1.94 File::Temp 0.16 OLE::Storage_Lite 0.13 IO::Stringy 2.110 I've attached a test script that throws the error and the test xsl file. The xls file comes from a customer so I don't know what created it. In the original xls file, there are more time columns. I cut out all but one (using Excel 2002 SP3) since the error seems to be thrown for every one of those. But just leaving one, the error is thrown just once. Dave Kubasiak Software Developer Comverge, Inc. dkubasiak@comverge.com www.comverge.com <<XLtester.pl>> <<test.xls>> This email and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this email in error, please notify the sender immediately by return email and delete it from your computer. Any views or opinions presented in this message or attachments are those of the author and do not necessarily represent those of the Company.
Download (untitled) / with headers
text/plain 117b
Hi Dave, Thanks for the clear bug report. I've identified a fix. It will be in the next (0.51) release. John. --
Download (untitled) / with headers
text/plain 224b
Hi, This issue has been fixed in version 0.51 of Spreadsheet::WriteExcel. http://cpansearch.perl.org/src/JMCNAMARA/Spreadsheet-ParseExcel-0.51/Changes Thank you for your help in identifying/fixing this issue. John. --


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.