versions yield different results
Hi Leif,
On Tue, Oct 12, 2010 at 10:58 AM, Leif Andersson
leif.anders...@sub.su.se wrote:
To change directly in code like this is totally no-no to many programmers.
If you feel uncomfortable with this, there are other methods doing the same
stuff
Library
Från: Al [ra...@berkeley.edu]
Skickat: den 12 oktober 2010 00:03
Till: perl4lib@perl.org
Ämne: MARC-perl: different versions yield different results
Example marc record is here:
http://www.mediafire.com/file/u5cxkrfwh9ew09z/example.zip
When I process
Hi Leif,
Is the downside to this approach that you are modifying a CPAN module
in place, or is it something to do with the behavior of 'use bytes'?
Would there be any undesirable side effects to adding 'use bytes' to
MARC::File::USMARC::encode on CPAN?
//Ed
On Tue, Oct 12, 2010 at 7:58 AM, Leif
. :-)
/Leif
Från: ed.summ...@gmail.com [ed.summ...@gmail.com] f#246;r Ed Summers
[...@pobox.com]
Skickat: den 12 oktober 2010 17:13
Till: perl4lib@perl.org
Ämne: Re: MARC-perl: different versions yield different results
Hi Leif,
Is the downside to this approach
On Tue, Oct 12, 2010 at 9:05 AM, Leif Andersson
leif.anders...@sub.su.se wrote:
To sum up.
I think it is a good idea to make the MARC blob a binary object, so to speak.
I don't know if you should just apply my simple hacks to CPAN code.
Or if it is called for a thourough re-write of some parts
When I process the record above in perl 5.8, MARC::Record version 1.38, and
Encode.pm version 2.12, the record comes out fine.
When I use perl 5.10, MARC::Record version 2.0.0, and Encode.pm 2.40 the
record comes out corrupted and MARC::Record will no longer read the result.
I tried it on