Stephen Clouse [EMAIL PROTECTED] wrote:
Under [mod_perl 2 and perl 5.10 on Fedora 9] I am getting some of the
most bizarre and insidious perl core errors I've ever seen in my 15
years of using perl.
Attempt to free unreferenced scalar: SV 0xbd266be4, Perl interpreter:
0xba01c410 at
On 9 Jul 2008, at 09:09, David Kaufman wrote:
# from the POD doco at
#
http://search.cpan.org/~gbarr/Scalar-List-Utils-1.19/lib/List/Util.pm#DESCRIPTION
$foo = first { defined($_) } @list; # first defined value in @list
Who needs to install a CPAN module to do that? I personally would
On Wed, 9 Jul 2008 13:23:13 +0100
Andy Armstrong [EMAIL PROTECTED] wrote:
On 9 Jul 2008, at 09:09, David Kaufman wrote:
# from the POD doco at
#
http://search.cpan.org/~gbarr/Scalar-List-Utils-1.19/lib/List/Util.pm#DESCRIPTION
$foo = first { defined($_) } @list; # first defined
Well, thank you for your advice, gentlemen. It got me on the right track,
and I did manage to figure out the issue today. You may or may not be
surprised to find it was this:
my $foo = bar if $baz;
Apparently one of the previous programmers left about 100 such constructs
littered about the
Mark Hedges wrote:
That's a normal thing. All installed modules put their
config into mods-available. Then you use `a2enmod` to
manage those symlinks and turn them on or off in
mods-enabled.
+1
I believe all Debian-based distributions have done this with Apache 2
for a few years now.
It
Yes, it's not obvious that you need to enable the module after
installing it. Why doesn't the installer enable it automatically?
-Original Message-
From: Colin Wetherbee [mailto:[EMAIL PROTECTED]
Sent: Thursday, 10 July 2008 12:52 PM
To: Mark Hedges
Cc: Paul Cameron;
On Wed, Jul 9, 2008 at 9:23 PM, Stephen Clouse [EMAIL PROTECTED] wrote:
We had Perl::Critic for the Perl side of the app, and I've done some hacks
to criticize the Mason code, but someone had disabled the
ProhibitConditionalDeclarations policy.
I'm thrilled to hear that this ultimately was
On Wed, Jul 9, 2008 at 11:05 PM, Perrin Harkins [EMAIL PROTECTED] wrote:
I'm thrilled to hear that this ultimately was valuable because I
suggested that policy. It would be great if you'd share your hack to
make Critic work on Mason code somewhere.
Oh, yeah, sure. Here's my test script.
A couple of months ago i was going through slides from gozers From
CGI to mod_perl 2.0, Fast! talk, which has some benchmarks comparing
CGI, perlrun and registry to each other. At which point i realized
that i've never really known how much faster using straight handlers
is than using one
