Re: Bug#356384: ITP: libtest-use-ok-perl -- Alternative to Test::More::use_ok
Marc 'HE' Brockschmidt wrote: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] writes: * Package name: libtest-use-ok-perl [...] Description : Alternative to Test::More::use_ok 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. . 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. Errr, both short and long description suck a lot. You're right. I hope that you planned to rewrite it before actually uploading the package, but generally, it would be nice to provide something that resembles the final Description in the ITP, so that peer-review can actually work. Thanks. We'll work out better description on debian-perl list. eloy -- [EMAIL PROTECTED] jak to dobrze, że są oceany - bez nich byłoby jeszcze smutniej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#356384: ITP: libtest-use-ok-perl -- Alternative to Test::More::use_ok
Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] writes: * Package name: libtest-use-ok-perl [...] Description : Alternative to Test::More::use_ok 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. . 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. Errr, both short and long description suck a lot. I hope that you planned to rewrite it before actually uploading the package, but generally, it would be nice to provide something that resembles the final Description in the ITP, so that peer-review can actually work. Thanks. Marc -- Cabal theories right: https://launchpad.net/distros/debian/+members Security is for whimps: https://launchpad.net/distros/ubuntu/+bug/34606/ Film at 11! pgpEW0W6qTSN3.pgp Description: PGP signature
Bug#356384: ITP: libtest-use-ok-perl -- Alternative to Test::More::use_ok
Package: wnpp Severity: wishlist Owner: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] * Package name: libtest-use-ok-perl Version : 0.01 Upstream Author : Autrijus Tang [EMAIL PROTECTED] * URL : http://mirrors.kernel.org/cpan/modules/by-module/Test/Test-use-ok-0.01.tar.gz * License : Perl: GPL/Artistic Description : Alternative to Test::More::use_ok 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. . 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. NOTE: this module is needed to upload new upstream version of libcatalyst-perl -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
