RE: use filetest anomaly

"Persico, Matthew O" <[email protected]>
Newsgroups gmane.comp.lang.perl.perl5.porters,gmane.comp.lang.perl.modules.dbi.sybase.devel
Message-ID <AB134D921E95C94F8BA6FDA616BE10020C83D69D@INCG2006A.corp.statestr.com>
> -----Original Message-----
> From: Dave Mitchell [mailto:[email protected]] 
> Sent: Monday, March 30, 2009 4:49 PM
> To: Matthew Persico
> Cc: Rafael Garcia-Suarez; pp; [email protected]; Persico, Matthew O
> Subject: Re: use filetest anomaly
> 
> On Mon, Dec 29, 2008 at 09:20:23PM -0500, Matthew Persico wrote:
> > On Mon, Dec 29, 2008 at 2:35 AM, Rafael Garcia-Suarez 
> > <[email protected]> wrote:
> > > 2008/12/29 Matthew Persico <[email protected]>:
> > >> Perl   - 5.10.0
> > >> $ ls -la ~/foo
> > >> -r-xr-xr-x   1 persicom develop        0 Dec 28 21:15 
> /home/persicom/foo
> > >>
> > >> Perl   - 5.10.0
> > >> $ perl -e 'if (-x "/home/persicom/foo"){print "got 
> it\n"}else{print 
> > >> "no got it\n"}'
> > >> got it
> > >>
> > >> Perl   - 5.10.0
> > >> $  perl -e 'use filetest "access";if (-x 
> > >> "/home/persicom/foo"){print "got it\n"}else{print "no got it\n"}'
> > >> no got it
> > >>
> > >> HUH?? What is borken about filetest "access" in 5.10? 
> Where should 
> > >> I report this? Any particular person, group or just use perlbug?
> > >>
> > >
> > > I believe that was fixed with :
> > >
> > > 
> http://camel.booking.com/perl.git/commitdiff/b376053de54af4268a31e5a
> > > 60d1f9e57db30af11
> > >
> > 
> > Hmm. Should I hand-patch that into my copy of 5.10.0, or is 
> 5.10.1 imminent?
> 
> 5.10.1 is still several weeks away.
> 

Thank you. I have already worked around it in the calling code that used
it by checking for both with and without trailing slash. I can wait
5.10.1.


--
Matthew O. Persico
Vice President
State Street IMS - Technology
Servicing Lazard Asset Management
30 Rockefeller Plaza, 49th Floor
New York, NY 10012
212 632 8255
[email protected]

 


> --
> The Enterprise's efficient long-range scanners detect a 
> temporal vortex distortion in good time, allowing it to be 
> safely avoided via a minor course correction.
>     -- Things That Never Happen in "Star Trek" #21
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.