On Mon, Dec 22, 2003 at 04:06:02PM -0800, Stas Bekman wrote:
> Use this archive instead:
Thanks for the link.
> Hmm, are you sure you've spelled things right? That's t/logs/error_log. Do
> you get anything at all written to it?
Yes, I do get some output written to the error_log. It turns out t
On Mon, Dec 22, 2003 at 04:02:20PM -0800, Stas Bekman wrote:
> By putting it last (after blib):
>
> it ensures that it'll be first in @INC. So it does it right.
Yes, of course, that makes sense. However, when I dump my @INC the blib
directories show up above the project/lib directory:
$VAR1 = [
William McKee wrote:
> On Mon, Dec 22, 2003 at 04:06:02PM -0800, Stas Bekman wrote:
>
>>Use this archive instead:
>
>
> Thanks for the link.
>
>
>
>>Hmm, are you sure you've spelled things right? That's t/logs/error_log. Do
>>you get anything at all written to it?
>
>
> Yes, I do get som
Stas,
A bit more testing has revealed more about modperl_inc.pl to me. I had
neglected to realize that modperl_inc.pl only gets loaded on server
startup. I had been running my tests using the following commands:
t/TEST -start
t/TEST -run-tests
When I made the changes to modperl_in
On Tue, Dec 23, 2003 at 10:12:49AM -0500, Geoffrey Young wrote:
> this is one danger of using the live-dev thing, you can get confused :) if
> you just follow the
>
> $ make && t/TEST t/foo.t -v
>
> paradigm you'll always get things right (I use an alias myself :). with
> smalish modules it sho
> However, I do like the idea of keeping the server
> running since it takes several seconds for my slow system to bring it
> up. Running `make && t/TEST -run-tests` seems to work fine though.
excellent. I don't use that feature myself, so it's good to know it's
working for people :)
--Geoff
William McKee wrote:
On Tue, Dec 23, 2003 at 10:12:49AM -0500, Geoffrey Young wrote:
this is one danger of using the live-dev thing, you can get confused :) if
you just follow the
$ make && t/TEST t/foo.t -v
paradigm you'll always get things right (I use an alias myself :). with
smalish modules i
William McKee wrote:
Stas,
A bit more testing has revealed more about modperl_inc.pl to me. I had
neglected to realize that modperl_inc.pl only gets loaded on server
startup. I had been running my tests using the following commands:
t/TEST -start
t/TEST -run-tests
That's the right p
On Tue, Dec 23, 2003 at 11:13:57AM -0800, Stas Bekman wrote:
> You did remember to enable Apache::Reload for your modules that are under
> development, didn't you? Without it the dev idea doesn't quite work.
Yeah, I did at least remember that one . That's why I can run make &&
t/TEST -run-tests.
On Tue, Dec 23, 2003 at 11:17:22AM -0800, Stas Bekman wrote:
> > t/TEST -start
> > t/TEST -run-tests
>
> That's the right paradigm.
It's a great paradigm!
> As you can see after modperl_inc.pl the @INC is correct ('lib' is first).
Yep. I should have mentioned that this version looks cor
10 matches
Mail list logo
