MARC::Lint has been updated (CVS version on SourceForge). I believe
the only change to the module itself is to the DATA section, which
should now reflect MARC 21 Update 5 (Oct. 2004).
--
Thank you,
Bryan Baldus
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://home.inwave.com/eija
At 1:05 PM -0600 1/23/05, Ed Summers wrote:
I added the new files to the [MARC::Lint] MANIFEST so make test would succeed.
I had forgotten to do this when I added files to MARC::Record for the
DOS EOF tests. The MARC::Record MANIFEST has now been updated.
--
Bryan Baldus
[EMAIL PROTECTED]
[EMAIL
On Mon, Jan 24, 2005 at 08:37:41AM -0600, Bryan Baldus wrote:
> I generally 'use warnings' or use the -w flag in the modules and scripts
> I've been writing. I didn't notice it was missing. I need to add strict and
> warnings to CodeData, as well. In modules/package files, is it practice to
> leave
>There were some unitialized variable warnings, nothing serious. 'make
>test' will run perl under the warnings pragma, so 'use warnings' in your
>module will help you catch this sort of thing early.
I generally 'use warnings' or use the -w flag in the modules and scripts
I've been writing. I didn'
On Sun, Jan 23, 2005 at 08:48:50AM -0600, Bryan Baldus wrote:
> The SourceForge CVS version of MARC::Lint has been updated with new
> checks (041, 043), revisions to check_245, a new internal
> _check_article method, the addition of MARC::Lint::CodeData (for 041,
> 043, etc.), and 2 new tests. W
The SourceForge CVS version of MARC::Lint has been updated with new
checks (041, 043), revisions to check_245, a new internal
_check_article method, the addition of MARC::Lint::CodeData (for 041,
043, etc.), and 2 new tests. Watch for further added check_xxx
methods in the near future, as I mov
