On Thu, Jul 2, 2009 at 4:03 PM, Michael G Schwern wrote:
> This is a quick release to sync with perl so 5.10.1 can release with a stable
> version number. It does NOT include the subtest() code in 0.89_01 (don't
> worry, it'll be back).
The attached patch does two things:
1.) Copy and paste the
else {
- print "skipping test on this platform\n";
+ print "${te}skipping test on this platform\n";
$files -= 1;
}
}
else {
$next += 1;
- print "FAILED at test $next\n";
+ print "${te}FAILED at test $next\n";
$bad = $bad + 1;
$_ = $test;
if (/^base/) {
[end of patch]
--
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
be runnable
from miniperl during the build before File::Glob exists.
I don't suppose there is a way to invoke at run-time the old-style
glob (which for us is really internal, not external)?
--
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
Here's what I get with today's snapshot, building with Compaq C V6.4-005 on
OpenVMS Alpha V7.2-1, -des configuration:
[.op]alarm..FAILED on test 4
[.op]glob...FAILED on test 8
[-.ext.encode.t]japaneseFAILED on test 18
[-.lib
At 03:28 PM 11/14/2001 -0500, Michael G Schwern wrote:
>On Wed, Nov 14, 2001 at 02:25:57PM -0600, Craig A. Berry wrote:
>>
>> OK, I've tried to reproduce the masking of SIGINT in C,
>Works fine on Linux, so I think you're on the right track.
Thanks.
>Don'
At 12:07 AM 11/9/2001 -0500, Michael G Schwern wrote:
>On Thu, Nov 08, 2001 at 11:03:45PM -0600, Craig A. Berry wrote:
>> At 10:18 PM -0500 11/8/01, Michael G Schwern wrote:
>> >Running bleadperl 12907 I'm getting some failures:
>> >
>> >ext/POSIX/t/po
Below is a working patch to magic.t, which gets all tests passing except:
# Use of uninitialized value in scalar assignment at [.op]magic.t line 244.
not ok 31
The code for that test looks like:
{
local $SIG{'__WARN__'} = sub { print "# @_\nnot " };
$! = undef;
ok 1;
}
A
At 11:56 AM 11/7/2001 -1000, Tim Jenness wrote:
>> not ok 28 # POSIX::errno(): 20, $!: 0
>>
>> which I think means autoloading sets errno but isn't supposed to. I suspect
>> it's doing a -d somewhere and leaving an errno of ENOTDIR laying about. Hmm.
>>
>
>Well, $! is meant to be exactly er
At 09:53 PM 11/7/2001 +0100, Tels wrote:
>So, if I read Tim correctly, make that my $foo = $! + 0; and it might
>pass the test. Needs probably a bit more munging to print the $! in
>numeric context as well as $foo after a failure.
Thanks Tels and Tim. With the following additional change:
---
I've made some progress getting this test to run (see working patch below)
but I still get one failure:
not ok 28 # POSIX::errno(): 20, $!: not a directory
20 is the correct value for ENOTDIR, but how can POSIX::errno() and $! be
expected to be numerically equal when $! returns a string? Or i
h the more recent Perl you're running.
Getting the logicals properly set up should take care of it.
--
Craig A. Berry
mailto:[EMAIL PROTECTED]
"Literary critics usually know what they're
talking about. Even if they're wrong."
-- Perl creator Larry Wall
At 5:04 PM -0700 9/24/01, Brad Hughes wrote:
>"Craig A. Berry" wrote:
>[...]
> > $ perl -"Twle" "my $foo = (values %ENV)[-1]; open(FILE, qq{>$foo})"
>> Name "main::FILE" used only once: possible typo at -e line 1.
>> In
At 11:59 AM 9/24/2001 -0400, Dan Sugalski wrote:
>At 11:23 PM 9/23/2001 -0500, Craig A. Berry wrote:
>>Basically we're pre-loading a hash when you use "keys" or "values" on
>>%ENV, and if I understand this right, hash elements are not
>>full-bl
ode where this is implemented
in vms/vms.c is pretty twisty stuff and I don't quite have a good
enough grasp of it yet to be sure this is right or know what to do
about it.
--
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
d, but do not know how to create a new TTY. #####
> Since two debuggers fight for the same TTY, input is severely entangled.
Yes, I've noticed that. It's not deleting from the environment
properly upon exit. There are not actually two debuggers running --
it just thinks there are. Or perhaps it's that it creates a new
entry in the list of debugger pids rather than recognizing that the
current process is already in the list:
$ show logical perldb_pids
"PERLDB_PIDS" = "541068861->541068861" (LNM$PROCESS_TABLE)
The other two bugs in the debugger I'm aware of are:
1.) There is a wayward system() call on start-up; I've searched in
vain for where this might be but can't see how it comes up with
"INFOCMP" as a command string.
2.) The exit codes used when quitting need some sort of translation on VMS.
These problems are visible here:
$ perl -de "exit;"
Loading DB routines from perl5db.pl version 1.14
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
main::(-e:1): exit;
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\INFOCMP\
DB<1> q
%SYSTEM-W-ILLSER, illegal service call number
--
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
At 6:46 PM -0400 9/22/01, Michael G Schwern wrote:
>On Sat, Sep 22, 2001 at 01:17:18PM -0500, Craig A. Berry wrote:
> > Most of these will be difficult or impossible to debug without
>> access to a VMS system.
>
>Oh ye of little faith. Give me the verbose output of e
ne by itself but
not in the test suite. vmsish.t #13 is a known bug in the "vmsish
'hushed'" pragma. I haven't gotten too far with the others but
can try to post detailed results if anyone is interested.
--
Craig A. Berry
17 matches
Mail list logo
