On Jan 27, 2006, at 6:06 PM, James E Keenan wrote:
Steffen Schwigon wrote:
Quite often -l (to read from lib/) is enough, depending on your
module
build complexity. For -b you have to call ./Build before prove,
which can be annoying and/or difficult to remember.
I'll have to try that out.
James E Keenan wrote:
Steffen Schwigon wrote:
Quite often -l (to read from lib/) is enough, depending on your module
build complexity. For -b you have to call ./Build before prove,
which can be annoying and/or difficult to remember.
I'll have to try that out. My modules all use MakeMaker
Greetings,
I've noticed that CPAN authors use a variety of
techniques to manipulate the run-time environment in
their test scripts. Usually, it involves changing
directories and/or altering @INC. This one seem pretty
popular:
BEGIN {
if($ENV{PERL_CORE}) { #What is PERL_CORE?
On Tuesday 24 January 2006 18:53, Jeffrey Thalhammer wrote:
Greetings,
I've noticed that CPAN authors use a variety of
techniques to manipulate the run-time environment in
their test scripts. Usually, it involves changing
directories and/or altering @INC. This one seem pretty
popular:
Jeffrey Thalhammer [EMAIL PROTECTED] wrote:
* Should a test script have a shebang? What should it
be? Any flags on that?
It's not at all neccessary, but IMHO it is good form; it's a surefire way
for anything else (HTTP server, IDEs, etc) to figure out that you're
actually a perl script and do
Jeffrey Thalhammer wrote:
* Should a test script have a shebang? What should it
be? Any flags on that?
I often see -t in a shebang. One downside of the shebang, though, is
that it's not particularly portable. As chromatic said, with prove
it's not really necessary. (prove -t)
*
On Tue, Jan 24, 2006 at 10:25:44PM -0500, David Golden wrote:
Jeffrey Thalhammer wrote:
* Should a test script have a shebang? What should it
be? Any flags on that?
I often see -t in a shebang. One downside of the shebang, though, is
that it's not particularly portable. As chromatic
