Re: buglet

[Jim H. <ha...@us...>]

Graham,
I made the problem go away by changing my code in the application.
Occasionally, it could pass an uninitiazed password on a bind.  What I had
included below was indeed line 204, but the statement continued over to
line 205.

This becomes a philosophical question of whether modules such
as your wonderful Net::LDAP should be responsible for seeing that things
passed to it are defined or not.  I can see both sides of the question.
Novices would be easily confused by such a message.  Old hand like me
should be able to figure things out for themseleves.  This popped up a few
minutes before I left for the day, so I fired off the question without
looking carefully at line 204 to see that it was continued on 205.  On the
other hand, the developer of a module cannot be expected to be continually
paranoid about what is passed.  Here are lines 204 and 205.

      return _error($ldap, $mesg, LDAP_INAPPROPRIATE_AUTH, "No password,
did you mean noauth or anonymous ?")
        if $type eq 'simple' and $passwd eq '';

  --Jim harle

On Wed, 9 May 2001, Graham Barr wrote:

> On Wed, May 09, 2001 at 04:52:23PM -0400, Jim Harle wrote:
> > When running an app that invokes warnings, I received:
> >
> > Use of uninitialized value at
> > /usr/local/lib/perl5/site_perl/5.005/Net/LDAP.pm line 204.
> >
> > This is with version 0.22, where line 204 is
> >
> > return _error($ldap, $mesg, LDAP_INAPPROPRIATE_AUTH, "No password, did you
> > mean noauth or anonymous ?")
>
> That does not make any sense. There is no use of any variables that would
> trigger the warning.
>
> Graham.
>