Thank a lot!
I'll both test the change, and negociate with the original author of
IonaLDAP.pm, to check he had no special reason to do that.
Marc
On Feb 26, 2007, at 4:49 AM, Marc Girod wrote:
Hello Graham,
Thanks again for your reply...
On 2/23/07, Graham Barr <[EMAIL PROTECTED]> wrote:
You should never call DESTROY directly.
I hear you, but do you have a pointer for me at documentation
explaining why this is wrong, what it may le
Hello Graham,
Thanks again for your reply...
On 2/23/07, Graham Barr <[EMAIL PROTECTED]> wrote:
You should never call DESTROY directly.
I hear you, but do you have a pointer for me at documentation
explaining why this is wrong, what it may lead to etc.?
Preferably to perl man pages...
[ Slig
Hello again,
On 2/22/07, Marc Girod <[EMAIL PROTECTED]> wrote:
Is it thus called anyway a second time?
Er... I did now the following, which got rid of the problem/symptom:
$ldap->DESTROY;
$ldap = 0;
Is it brutal?
Too brutal?
Marc
Thank You Graham,
On 2/21/07, Graham Barr <[EMAIL PROTECTED]> wrote:
The only safe way to solve this is to ensure that all your objects are
destroyed before global destruction.
I hear what you say, and I believe I understand it.
However, my attempt fails. In my user script, I added in the end
On Wed, February 21, 2007 8:18 am, Marc Girod wrote:
> (in cleanup) Can't call method "FETCH" on an undefined value at
> /usr/lib/perl5/site_perl/5.8.5/Net/LDAP.pm line 266 during global
> destruction.
>
> Also, I thought I could provide bits of the package code I use:
> sub DESTROY {
>
Hello again,
On 2/21/07, Marc Girod <[EMAIL PROTECTED]> wrote:
...
The version of LDAP.pm I use is:
I downloaded and installed perl-ldap-0.34 (without at least some of
the possible optional modules: Authen::SASL, GSSAPI, IO::Socket::SSL ,
XML::SAX::Writer.
All the tests were successful (10 ski
