Re^2: Issues when testing module loading

Thanks for that reply - yes if I were distributing things using a Makefile.PL then this would be a non-issue. But right now I distribute things as Debian packages, and raw .tar.gz files.

(This particular case came up when I made a new release of my chronicle blog compiler.)

Changing my test case to read as follows still fails though:

#/usr/bin/perl -w
#
use strict;
use warnings;
no warnings "all";
use Test::More qw( no_plan );

BEGIN{ use_ok( 'CGI' ); }

BEGIN{ use_ok( 'Date::Format' ); }

BEGIN{ use_ok( 'POSIX' ); }
[download]

Steve
--

Comment on Re^2: Issues when testing module loading Download Code

Replies are listed 'Best First'.
Re^3: Issues when testing module loading by moritz (Cardinal) on Jun 03, 2008 at 16:16 UTC
my bad, warnings only effects the lexical scope, and the warnings are generated inside the POSIX module. One workaround is to explicitly only import a non-conflicting sub `BEGIN{ use_ok( 'POSIX', 'setsid' ); }`. Or use `require_ok`, which doesn't import anything. Or don't test for POSIX at all, it's been core since perl 5, and not likely to go away any time soon.	[reply] [d/l] [select]
Re^4: Issues when testing module loading by skx (Parson) on Jun 03, 2008 at 18:48 UTC
I will stop testing for POSIX, as you suggest. (The test file is automatically generated; but I can add an exception to it without too much difficulty!) Steve --	[reply]