pkgsrc/devel/p5-Test-use-ok/distinfo

$NetBSD: distinfo,v 1.1.1.1 2008/06/23 03:59:19 abs Exp $

SHA1 (Test-use-ok-0.02.tar.gz) = 3a4e9a4361ab9118a2469476ca42434030710bf0
RMD160 (Test-use-ok-0.02.tar.gz) = f0adc7074c4afd2440f14a64cb47b5f30f7c1944
Size (Test-use-ok-0.02.tar.gz) = 13348 bytes
Import p5-Test-use-ok-0.02 According to the Test::More documentation, it is recommended to run use_ok() inside a BEGIN block, so functions are exported at compile-time and prototypes are properly honored. That is, instead of writing this: use_ok( 'Some::Module' ); use_ok( 'Other::Module' ); One should write this: BEGIN { use_ok( 'Some::Module' ); } BEGIN { use_ok( 'Other::Module' ); } However, people often either forget to add BEGIN, or mistakenly group use_ok with other tests in a single BEGIN block, which can create subtle differences in execution order. With this module, simply change all use_ok in test scripts to use ok, and they will be executed at BEGIN time. The explicit space after use makes it clear that this is a single compile-time action. 2008-06-23 05:59:19 +02:00			$NetBSD: distinfo,v 1.1.1.1 2008/06/23 03:59:19 abs Exp $

			`SHA1 (Test-use-ok-0.02.tar.gz) = 3a4e9a4361ab9118a2469476ca42434030710bf0`
			`RMD160 (Test-use-ok-0.02.tar.gz) = f0adc7074c4afd2440f14a64cb47b5f30f7c1944`
			`Size (Test-use-ok-0.02.tar.gz) = 13348 bytes`