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 chr
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")
*
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
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
> popula
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"?
