Bug #35331 for perl-ldap: EOF behaviour on empty files

Wed Apr 23 06:57:37 2008 joaocosta [...] zonalivre.org - Ticket created

Subject:

EOF behaviour on empty files

The eof method returns false when the LDIF object is initialised with an empty file.

Wed Apr 23 07:30:56 2008 gbarr [...] pobox.com - Correspondence added

Subject:	Re: [rt.cpan.org #35331] EOF behaviour on empty files
Date:	Wed, 23 Apr 2008 06:30:15 -0500
To:	bug-perl-ldap [...] rt.cpan.org
From:	Graham Barr <gbarr [...] pobox.com>

On Apr 23, 2008, at 5:57 AM, Joao Costa via RT wrote: Show quoted text

> The eof method returns false when the LDIF object is initialised > with an > empty file.

Please given a sample of code to demonstrate what you mean by initialized ? open(my $fh, "empty_file"); could be considered initializing the file handle $fh with an empty file but eof($fh) is not true until oyu try to read from it. Graham.

Wed Apr 23 07:30:58 2008 The RT System itself - Status changed from 'new' to 'open'

Wed Apr 23 08:21:12 2008 joaocosta [...] zonalivre.org - Correspondence added

From:

joaocosta [...] zonalivre.org

On Wed Apr 23 07:30:56 2008, gbarr@pobox.com wrote: Show quoted text

> Please given a sample of code to demonstrate what you mean by > initialized ?

Maybe i meant instantiated instead of initialised. For instance: ------------------------------------------ use Net::LDAP::LDIF; $ldif = Net::LDAP::LDIF->new( "file.ldif", "r", onerror => 'undef' ); while( not $ldif->eof ( ) ) { $entry = $ldif->read_entry ( ); } ------------------------------------------ If "file.ldif" is empty, the loop above still runs once, which i thought was odd. Not sure if it's the intended behaviour or not, but i was assuming the code inside the loop would not run when "file.ldif" is empty. Thanks for taking your time to look at this.

Thu Mar 11 21:32:40 2010 GBARR [...] CPAN.ORG - Status changed from 'open' to 'resolved'