So, when is 5.6.1 scheduled to release?

> -----Original Message-----
> From: Craig A. Berry [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 24, 2000 5:45 PM
> To: Jordan Henderson
> Cc: [EMAIL PROTECTED]
> Subject: testing Perl (was RE: VMS Perl bug (?) report)
> 
> 
> At 03:29 PM 7/24/00 -0400, Jordan Henderson wrote:
> >I complained a lot about the state of Perl recently, but I 
> do realize that if
> >Perl is to work for _me_ then _I_ had better help bake the bread.
> >
> >Can all those who have made patches necessary for 5.6.0 or 
> know of patches that
> >are needed for 5.6.1 (for example, the one that Dan Sugalski 
> dug up for the guy
> >whose perl wouldn't start due to an environment problem 
> hanging Perl startup,
> >email about this one is attached) speak up?  I'll promise to 
> put together a
> >system that I'll test all my stuff against.
> 
> Peter offers instructions for building the closest thing to 
> an up-to-date 
> test kit at:
> 
<http://www.best.com/~pvhp/vms/cfgperl_6409/>

That should include all the patches to 5.6.0, though I can't guarantee 
everything is in there.  Actually, a quick check shows that Chuck Lane's 
piping stuff is *not* in there.  Charles Bailey was, in his words, "working 
them into the repository," but had also expressed some doubt about the 
AST-reentrancy of the C RTL that Chuck's code depends on.  I don't remember 
when Charles said he would return from his month away with other duties or 
whether it will be before 5.6.1 goes final.

>Subject: RE: Perl hangs on OpenVMS

I think pretty much all of the posts on this subject, including mine, have 
been wrong.  We don't really know for sure whether it is a Perl bug or a VMS 
rightslist /$getjpi bug, but I suspect the latter.  If Dan did in fact come 
up with patches I have not seen them posted here.  I have looked long and 
hard at Charles Bailey's original code and it looks good to me.  His 
suggested fix from Nov. '98 (which I repeated) does not look right since it 
assigns a value that will immediately be overwritten by the $getjpiw call.  

The poster of the original query in Nov. '98 says that his problem derived 
from having no system identifiers defined:

<http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/1998-12/msg00013.html>

I don't know if this was the case for the more recent problem.  If so, 
perhaps what we need is a panic test and abort after executing the loop in 
vms_image_init() a few thousand times.

_______________________________________________
Craig A. Berry                                   
mailto:[EMAIL PROTECTED]

Reply via email to