> From: Bryan Baldus [mailto:[EMAIL PROTECTED]
> Sent: 18 August, 2004 09:24
> Subject: Warnings during decode() of raw MARC
>
> I'm probably missing something obvious, but I have been
> unsuccessful in trying to capture the warnings reported by
> MARC::Record that are set by MARC::File::USMAR
On Wed, Aug 18, 2004 at 08:23:59AM -0500, Bryan Baldus wrote:
> Both seem to fail to capture the warnings reported by MARC::File::USMARC.
There appears to be a bug in MARC::Batch::next() code at line 123 which
extracts the warnings from the newly instantiated MARC::Record object
and stuffs them in
On Wed, Aug 18, 2004 at 12:56:17PM -0500, Bryan Baldus wrote:
> Ok, I'll try to provide a test file. However, since I've been using MacPerl
> (and Windows), I don't usually deal with test files (the usual
> perl Makefile.PL
>make
>make test
>make install
> doesn't usually work for me,
>How do you typically do the install? MARC::Record is included at the
>ActiveState PPM Repository, so it should do these things on a Windows
>platform...assuming nmake or some sort of make variant is being used.
At home (on the Mac), I just drop the MARC folder in my site_lib folder in
the MacPer
> ... I've not usually bothered to look at how the tests or the
> Makefile.PL work. This is one reason I haven't tried to distribute my
> modules through CPAN.
What no OS X yet!? The drag and drop trick is what you are stuck with
in MacPerl, and it's kind of a testament to Perl's flexibility that