I have tried to change the filter handler merging rules so that we can
complain about connection filters places inside resource container, but while
it worked OK for resources running under modperl (by tweaking the dir_config
merging), it doesn't work for non-modperl resources, since we don't co
Tom Schindl wrote:
Ok. I see your point and that's why I'd vote for your second suggestion:
$socket->recv:
* obj: $socket
* arg1: $len
and so it'll be. Thanks for the feedback, Tom.
--
__
Stas BekmanJAm_pH --> Just A
David Wheeler <[EMAIL PROTECTED]> [12-05-2004 01:25]:
> On May 11, 2004, at 3:24 PM, Geoffrey Young wrote:
[...]
>> yeah, you can probably just check for DIR_MAGIC_TYPE here.
> Cool, saves the expense of the stat! Here's what I have now:
[...]
> return DECLINED unless $r->content_type == DIR_MA
On Mon, Mar 15, 2004 at 10:46:07AM -0800, Stas Bekman wrote:
> Philippe M. Chiasson wrote:
> >On Wed, 2004-03-10 at 15:42, Stas Bekman wrote:
> >
> >>rbb is back to the game and he brings gcov (test coverage) for the apr
> >>test suite:
> >>http://apr.apache.org/coverage/index.html
> >>I wonder i
Stas Bekman wrote:
Tom Schindl wrote:
Stas Bekman wrote:
Tom Schindl wrote:
[...]
Creating API-documentation like java has one is very common and the
same is true for UML where one does not add an arg0: obj because it's
implied in Object Oriented Contexts.
Besides that. I've already created o
Tom Schindl wrote:
Stas Bekman wrote:
Tom Schindl wrote:
[...]
It doesn't matter to me. If you prefer to have:
* obj: $socket
* arg1: $len
I'd also prefer to have it this way. How does this look like for
static methods?
* class: APR::SOCKET
* arg1: $len
You mean for something like:
Apache->
Stas Bekman wrote:
Tom Schindl wrote:
[...]
It doesn't matter to me. If you prefer to have:
* obj: $socket
* arg1: $len
I'd also prefer to have it this way. How does this look like for
static methods?
* class: APR::SOCKET
* arg1: $len
You mean for something like:
Apache->warn(@msg);
you sug
Tom Schindl wrote:
[...]
It doesn't matter to me. If you prefer to have:
* obj: $socket
* arg1: $len
I'd also prefer to have it this way. How does this look like for static
methods?
* class: APR::SOCKET
* arg1: $len
You mean for something like:
Apache->warn(@msg);
you suggest to have:
class:
Stas Bekman wrote:
Geoffrey Young wrote:
the only thing I find strange is arg1, which is always the object.
while ->
makes $self the first argument to the send() subroutine in the strict
perl
sense, from the user standpoint the first argument to the send()
method is
really $buf.
Well, the obje
