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.
Owner: |
Nobody in particular
|
Requestors: |
sripad.sambrani [...] actel.com
|
Cc: |
|
AdminCc: |
|
|
Severity: |
(no value)
|
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
image001.gif
utility_pm.PNG
|
Tue Mar 10 19:05:45 2009
sripad.sambrani [...] actel.com - Ticket created
Message body is not shown because sender requested not to inline it.
Hi,
Please note the following with regard to the PERL module Utility.pm.
While testing my script using MSExcel parser on Linux platform, following
messages were reported on console.
Use of uninitialized value in substitution (s///) at
/soft/gnu-os/perl-5.8.0/lib/site_perl/5.8.0/Spreadsheet/ParseExcel/Utility.
pm line 183.
Use of uninitialized value in substitution (s///) at
/soft/gnu-os/perl-5.8.0/lib/site_perl/5.8.0/Spreadsheet/ParseExcel/Utility.
pm line 188.
Use of uninitialized value in length at
/soft/gnu-os/perl-5.8.0/lib/site_perl/5.8.0/Spreadsheet/ParseExcel/Utility.
pm line 209.
When Utilty.pm at my installation path was checked, it was observed to have
the contents marked in the attached file utility_pm.PNG. Please note this
is captured after opening the module in VIM and hence shows line numbers in
the left column. Also note the comment on line 170 in context of line 171,
shown below for reference.
# TODO. Replace string eval with a function.
$section = eval "$number $conditional" ? 0 : 1;
I observe variable $section (line 171 shown above) remains uninitialized on
account of missing function for eval. This variable, in turn, is used to
extract required format in variable $format (refer line 175 in file
attached). Hence the messages shown were reported for $format on lines 183,
188 & 209. Please clarify.
Regards,
Sripad.
Mon Mar 30 13:31:52 2009
jmcnamara [...] cpan.org - Correspondence added
Hi,
Thanks for that.
Could you send me the Excel files that produces the error.
John.
--
Mon Mar 30 13:31:53 2009
The RT System itself - Status changed from 'new' to 'open'
Wed Aug 19 07:47:58 2009
jmcnamara [...] cpan.org - Correspondence added
Hi,
Can you send the Excel file that produces this error.
It will be impossible to locate the issue without it.
John,
--
Wed Aug 19 08:24:35 2009
jmcnamara [...] cpan.org - Correspondence added
On Wed Aug 19 07:47:58 2009, JMCNAMARA wrote:
Show quoted text> Hi,
>
> Can you send the Excel file that produces this error.
>
> It will be impossible to locate the issue without it.
>
Hi,
It seems that this is the same bug as the following, in which case you
don't need to send a sample file.
https://rt.cpan.org/Ticket/Display.html?id=45009
There will be a fix for this issue in version 0.51.
John.
--
Thu Aug 20 05:25:18 2009
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'