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: |
MTHURN [...] cpan.org
|
Cc: |
|
AdminCc: |
|
|
Severity: |
Important |
Broken in: |
|
Fixed in: |
(no value)
|
|
Tue Apr 03 18:30:56 2007
MTHURN [...] cpan.org - Ticket created
I have no idea why this suddenly started happening:
Base class package "Spreadsheet::ParseExcel::Workbook" is empty.
(Perhaps you need to 'use' the module which defines that package first.)
at C:/Perl/site/lib/Spreadsheet/ParseExcel/SaveParser.pm line 14
BEGIN failed--compilation aborted at
C:/Perl/site/lib/Spreadsheet/ParseExcel/SaveParser.pm line 14.
--
- - Martin 'Kingpin' Thurn
Tue Apr 03 20:25:50 2007
MTHURN [...] cpan.org - Correspondence added
Maybe this happened whey I upgraded from ActivePerl build 819 to build
820? In any case, you can fix it by adding "use
Spreadsheet::ParseExcel;" at the top of SaveParser.pm...
--
- - Martin 'Kingpin' Thurn
Tue Apr 03 20:26:01 2007
MTHURN [...] cpan.org - Status changed from 'new' to 'open'
Fri Apr 20 04:08:43 2007
ntyni [...] iki.fi - Correspondence added
On Tue Apr 03 18:30:56 2007, MTHURN wrote:
Show quoted text> Base class package "Spreadsheet::ParseExcel::Workbook" is empty.
> (Perhaps you need to 'use' the module which defines that package
first.)
Show quoted text> at C:/Perl/site/lib/Spreadsheet/ParseExcel/SaveParser.pm line 14
> BEGIN failed--compilation aborted at
> C:/Perl/site/lib/Spreadsheet/ParseExcel/SaveParser.pm line 14.
This is breaking DBD::Excel 0.06, which has
require Spreadsheet::ParseExcel::SaveParser;
without using Spreadsheet::ParseExcel itself. See Debian bug #420037,
http://bugs.debian.org/420037 .
Adding 'use Spreadsheet::ParseExcel' in
lib/Spreadsheet/ParseExcel/SaveParser.pm indeed fixes this regression.
Cheers,
--
Niko Tyni (on behalf of the Debian Perl Group)
ntyni@iki.fi
Tue Oct 28 11:58:40 2008
jmcnamara [...] cpan.org - Correspondence added
Tue Oct 28 11:58:43 2008
jmcnamara [...] cpan.org - Status changed from 'open' to 'resolved'