On Tue, Dec 6, 2011 at 3:55 PM, Desilets, Alain
wrote:
> No, I meant more things like this:
>
> ---
>
> package MyClass;
>
> my $class_level_attribute;
>
> sub new {
> my ($class) = @_;
> $self->{instance_level_attribute} = undef;
> bless $self, $class;
> return
> > But declaring a variable as "my" is not sufficient to prevent it from being
> > persistent. You can declare a package variable with "my" and it will
> > persist.
>
> That's true! I assume you mean this:
>
> my $foo = 7;
>
> sub print_foo {
> print $foo;
> }
>
> That's called a closure.
On Tue, Dec 6, 2011 at 3:11 PM, Desilets, Alain
wrote:
> I'm using Windows. In my experience, modules that don't work well with
> multithread, also don't work well with fork, and vice-versa.
I wouldn't expect that. In a multi-process situation, files and
sockets are not shared unless you opened
> > On Tue, Dec 6, 2011 at 5:35 AM, Desilets, Alain
> > wrote:
> >> However, even those high quality CPAN modules can fall flat on their face
> >> when > they are used in contexts that they weren't designed for. For
> >> example, I recently > discovered that several CPAN modules cannot be used
(cc'ing the mod_perl list on this one also, please remember to reply all :)
On Tue, Dec 6, 2011 at 11:28 AM, Dr James A Smith wrote:
> On 06/12/2011 19:09, Fred Moyer wrote:
>> (cc'ing mod_perl list)
>>
>> On Tue, Dec 6, 2011 at 5:35 AM, Desilets, Alain
>> wrote:
>>> Thx to Fred, Andre and Jon f
> On Tue, Dec 6, 2011 at 5:35 AM, Desilets, Alain
> wrote:
>> However, even those high quality CPAN modules can fall flat on their face
>> when they are used in contexts that they weren't designed for. For example,
>> I recently discovered that several CPAN modules cannot be used safely in a
>>
(cc'ing mod_perl list)
On Tue, Dec 6, 2011 at 5:35 AM, Desilets, Alain
wrote:
> Thx to Fred, Andre and Jon for answering. BTW: I hope I didn't offend anyone.
> What I really meant was:
No offense taken at all. Welcome to mod_perl!
>
> "Is it me or is mod_perl *much more slippery than standa
(I have read the bug reporting guides but unfortunately cannot follow all the
instructions because I am missing Apache::TestReportPerl and do not have the
necessary permissions to install it, nor to rebuild perl with debugging turned
on. Hopefully I have provided enough information.)
I have di
