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(

    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;


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:

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: 42425
Status: resolved
Worked: 30 min
Priority: 0/
Queue: Spreadsheet-ParseExcel

Owner: Nobody in particular
Requestors: WIGS [...]

Bug Information
Severity: Important
Broken in:
  • 0.44
  • 0.45
Fixed in: (no value)

Subject: Undesirable use of $& variable within Spreadsheet::ParseExcel
Download (untitled) / with headers
text/plain 456b
Spreadsheet/ParseExcel/ internally uses the $& (aka $MATCH) variable, which introduces a known performance hit to all regular expression matches in any application that has loaded Spreadsheet::ParseExcel. This applies even to regular expressions outside of the Spreadsheet::ParseExcel libraries. Attached is a proposed patch to that eliminates the use of $&. Regretably, there are no regression tests for the modified lines of code.
application/octet-stream 1.8k

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 355b
On Wed Jan 14 19:31:03 2009, WIGS wrote: Show quoted text
> Spreadsheet/ParseExcel/ internally uses the $&
Ouch. Thanks for that. I've only just begun to work my way through the cruft. Show quoted text
> Regretably, there are no regression tests for the modified lines of code.
Not to worry. The existing code wouldn't pass a regression test either. John. --
Hi, Fixed in version 0.46. Thanks, John. --

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

Please report any issues with to