Peter,  

What we have noticed is; perl v5.8.0 $FindBin::Bin is returning
"/usr/local/bin" and perl v5.8.5 $FindBin::Bin is returning
"/usr/local/bin/"

The next "/" at the end of bin.

Dave Yeoman
System Engineer - Enterprise Performance
Galileo International
Phone:  (303) 397-5721
E-mail: [EMAIL PROTECTED] 


-----Original Message-----
From: Steve Peters via RT [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 30, 2005 1:50 PM
To: Yeoman, Dave
Subject: Re: [perl #37029] Perl bug - help

On Tue, Aug 30, 2005 at 06:51:22AM -0700, Yeoman, Dave wrote:
> # New Ticket Created by  "Yeoman, Dave" 
> # Please include the string:  [perl #37029]
> # in the subject line of all future correspondence about this issue. 
> # <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37029 >
> 
> 
> I'm by no means an expert with perl, but I need some Perl help.  We have
one
> x440 server with RH 3.0.5 and perl v5.8.0 built for
> i386-linux-thread-multiand and another server x445 upgraded with RH 4.0
perl
> v5.8.5 built for i386-linux-thread-multi.  The server with Perl v5.8.5
> produces different results from the pop (line 458 below) and I'm not sure
> why.  Can you help answer my question?
> 
>  

If C<pop()> is returning different results, then the array it is pop'ping
off
of is likely getting populated in a different order, or with different
results.
>From what you've included, though, its hard to say.  How are the results
different in 5.8.5 from 5.8.0?

Steve Peters
[EMAIL PROTECTED]

The information in this electronic mail message is sender's business
Confidential and may be legally privileged. It is intended solely for the
addressee(s). Access to this Internet electronic mail message by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it is prohibited and may be unlawful.  
The sender believes that this E-mail and any attachments were free of any
virus, worm, Trojan horse, and/or malicious code when sent. This message and
its attachments could have been infected during transmission. By reading the
message and opening any attachments, the recipient accepts full
responsibility for taking protective and remedial action about viruses and
other defects. Cendant is not liable for any loss or damage arising in any
way from this message or its attachments.

Reply via email to