On Sat, 5 Jan 2002, Stas Bekman wrote:
I thought his question was abouthow to make INC private
to various vh's. The answer is that it's done.
Have I misinterpreter the question? Or are we talking
about different things?
ah, i must have misread the last message.
of course, there is still a
On Sat, 5 Jan 2002, Stas Bekman wrote:
Guys, I suggest that you read the design docs before you
continue. The INC issue has been addressed already.
Please read:
http://apache.org/~dougm/modperl_2.0.html
http://apache.org/~dougm/modperl_design.html
that may not be exactly what he's wishing
On Sun, 7 Oct 2001, Stas Bekman wrote:
We have had two new designs worked out long time ago,
but one has been picked by take23.org and the other
wasn't applied. (hi brian)
:(
sorry! i have this tendency to bite off more than i can
chew. i have 10 projects and none of them will ever be
On Tue, 17 Jul 2001, Vivek Khera wrote:
Awww, come on Stas! Juice, not beers! I certainly
don't want my next mod_perl designed by a bunch of
drunken hackers reading code upside down. ;-)
# XXX: drunk, fix later
I'll miss you guys this year... got a family wedding to
attend in Ontario...
On Mon, 25 Jun 2001, Doug MacEachern wrote:
whenever. of course, then we have the problem of docs
containing docs based on the code in cvs, not the
current release of modperl.
yeah, i think that's the worst outcome.
i have the opposite feeling, docs interspersed amongst
subs drives me
On Mon, 25 Jun 2001, Doug MacEachern wrote:
that's cool, 1.x has similar:
skip_test unless have_module 'Foo';
yeah i knew i horked the concept from you somewhere along
the line :)
i just found it shorter/cleaner to write:
plan tests = 6, \condition;
especially since condition can be
On Sun, 24 Jun 2001, Stas Bekman wrote:
the only way to ensure identical order from run to run,
across different systems (and changes in file inodes
ordering) is to explicitly list the tests in the wanted
order. otherwise it's up to the inodes order under ./t.
Since I mess with tests
fwiw, i've come up with a couple of other useful shorthand
routines for my Wombat::Test package:
sub have_lib {
for (@_) {
unless (eval require $_) {
$@ = $_ not found\n if $@ =~ /^Can't locate/;
return undef;
}
}
return 1;
}
On Sun, 24 Jun 2001, Stas Bekman wrote:
ok will add 'sort'. which will presort tests before
applying any other algorithm.
should 'sort' be non-exclusive with 'rotate|repeat'? (it
won't apply to 'random' of course)
but it gets hairy then: --run-tests[=[N][:][order][:][sort]] ?
I'd rather
On Sun, 24 Jun 2001, Stas Bekman wrote:
already there more or less. See perldoc Apache::Test in
cvs.
my skip_all unless have_lib is just shorthand for a very
common requirement. it shouldn't replace the more general,
powerful and verbose plan unless condition, but it does
save a lot of typing
On Sun, 24 Jun 2001, Stas Bekman wrote:
I understand. Another option would be to always sort the
tests unless you have specified their order on the
command line.
o if you specify none -- everything is sorted.
o if you specify only dirs -- evething within dirs is sorted, dirs order
is
On Sat, 23 Jun 2001, Doug MacEachern wrote:
i'm pretty sure cvs allows access control so certain
people can write to docs/ but not ../
it doesn't actually; you have to rely on unix permissions.
would you really trust somebody to write docs that you
wouldn't trust to write code? i wouldn't.
On Mon, 21 May 2001, Gerald Richter wrote:
I agree to Matt, there is nothing missing for an
application server, it's mainly a matter of installation
and documentation, so for people not familar with CPAN
it's maybe hard to find.
you're both missing my point. sure there are lots of
On Wed, 14 Feb 2001, Doug MacEachern wrote:
On Sun, 11 Feb 2001, Stas Bekman wrote:
Brian, will you have a chance to commit Apache::LogSTDERR to CPAN or
mod_perl source? You said you will, it's still not there, so I'm kinda
puzzled whether to document this one in the book or not. Thanks.
14 matches
Mail list logo
