On Sun, 24 Jun 2001, Stas Bekman wrote:
Running a stand-alone:
$ make xs_generate
yeah, that isn't meant be used at the moment.
unfortunately 'make source_scan' shocks with:
Expecting parenth after identifier in `apr_sms_t **sms'
after `apr_sms_t ' at
-Original Message-
From: Doug MacEachern
To: Geoffrey Young
Cc: '[EMAIL PROTECTED]'
Sent: 6/25/01 7:46 PM
Subject: RE: Apache::Util stuff
On Mon, 25 Jun 2001, Geoffrey Young wrote:
ok, I did lots of playing around and have come full circle. my
problem
seems to be that
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
- something else to look into, a recent bug has been introduced, if
t/TEST -run=2 starts the server, when $SIG{INT} is caught it should
stop the server but does not at the moment.
I don't understand why would you want to do that. --run-tests is already a
non-standard execution,
On Mon, 25 Jun 2001, Doug MacEachern wrote:
On Sun, 24 Jun 2001, Stas Bekman wrote:
So what do we decide about documentation style, so we can start
documenting things as we go? As I've replied to brian's email, I'm in
favor of inline docs if it doesn't make the code harder to read.
On Mon, 25 Jun 2001, Doug MacEachern wrote:
On Sun, 24 Jun 2001, Stas Bekman wrote:
Running a stand-alone:
$ make xs_generate
yeah, that isn't meant be used at the moment.
ok
unfortunately 'make source_scan' shocks with:
Expecting parenth after identifier in `apr_sms_t **sms'
