At 02:31 PM 7/24/00 -0700, Peter Prymmer wrote:
>Oops. I was assuming that Charles Lane's pipe stuff would have made it
>into Jarkko's cfgperl, but of course vmsperl is a separate branch. You'll
>need to see www.crinoid.com for Charles Lanes' stuff.
It's not clear to me whether the piping patches aren't there because Charles
has not worked them in or because he has worked them in to a repository that
has not been synched with Jarkko's.
>Also: I do not have a copy of your File::Temp work posted at best.com
>as yet (I'll try to place it there this evening
thanks, feel free to push it further if you've got the tuits :-)
>> >Subject: RE: Perl hangs on OpenVMS
>
>> 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.
>
>You want to keep track of the number of times that vms_image_init()
>is called?
Nope. Not the number of calls, but the number of times it loops over
$getjpiw. It will only enter the loop at all if it doesn't get all the
identifiers on the first pass. I can't think of any valid reason it would
loop more than a handful of times, thus my suggested panic test. I see that
Jordan has chimed in, and he is no doubt right there is a better way to do
this. I will respond separately to his comments.
>Speaking of panic: the problem with t/lib/require.t is not unique to VMS
>and has cropped up on Solaris and elsewhere. Hence the fix ought to be a
>perl internals fix (which for all I know has already been posted.
Good to hear.
>The successor to 5.6.0 is due out within a few weeks (less than a month).
Thanks, I was wondering about that too.
_______________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
