On Thu, 15 Sep 2005 18:31:43 +0530, Sastry [EMAIL PROTECTED] wrote
Hi Sadahiro
Having incorporated the changes in the doop.c and op.c
I strangely get lots of failures and here are the test results. Seems
like the first approach itself fails on tr// and there will certainly
[EMAIL PROTECTED] - Mon Sep 12 04:13:08 2005]:
I was not aware that the Windows® Server 2003 SP1 Platform SDK can be
used with WinXP (SP2). I have unfortunately not seen the remark on the
downloadpage:
This edition of the SDK replaces the previous SDKs for Windows XP SP2
and Windows
# New Ticket Created by Smylers
# Please include the string: [perl #37199]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37199
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of
Please find attached the patch I alluded to in the perlbug submission.
Smylers
--
May God bless us with enough foolishness to believe that we can make a
difference in this world, so that we can do what others claim cannot be done.
File-Basename_doc.patch
Description: Binary data
Nicholas Clark (via RT) wrote:
Using -DT with use warnings; goes bang on OS X. I was able to get out of
memory failures on FreeBSD, but everything works on x86/Linux, at least for
me. I guess x86/Linux is just lucky - this seems to be a real bug, although
quite where, I'm not sure.
Starting
On 9/18/05, Geoff Mottram [EMAIL PROTECTED] wrote:
The problem with regular expressions getting clobbered only occurs while
running Perl with the -d (debug) option. I believe it is the sub()
method of the DB.pm module that contains the regular expression that
clobbers the running script's
On 9/19/05, John E. Malmberg [EMAIL PROTECTED] wrote:
When I enable hard links on VMS, it exposed that the t/io/fs.t is not
testing what the comments indicate that it is testing.
The correct test would be to see if the $mode of the third link matched
the $mode for the original file.
What
Yitzchak Scott-Thoennes wrote:
bleadperl is getting:
DProf.xs:140: warning: `unused' attribute ignored
The following fixes it; I thought about defining a pTHX_bare in
perl.h that leaves off the register and PERL_UNUSED_DECL from pTHX,
but decided there really wasn't going to be a lot of
On Sat, Sep 17, 2005 at 11:31:11AM -0700, Nicholas Clark wrote:
Using -DT with use warnings; goes bang on OS X. I was able to get out of
memory failures on FreeBSD, but everything works on x86/Linux, at least for
me. I guess x86/Linux is just lucky - this seems to be a real bug, although
quite
Thanks for your bug report and patch.
However, the mangled NAME section has already been fixed in the current
development version of Perl, along with a great many other improvements
to File::Basename and its documentation.
The latest version can be found at the following URL:
On 9/18/05, John E. Malmberg [EMAIL PROTECTED] wrote:
I am looking for comments on a couple of VMS specific behavior issues.
Unless there are some objections, I would like to make these changes:
They all seem sensible to me. (Although I don't understand the 2nd
very well, but I trust the
Automated smoke report for 5.8.7 patch 25494
Mugwump.uk.radan.com: Intel(R) Pentium(R) 4 CPU 3.40GHz(~3391 MHz) (x86/2 cpu)
onMSWin32 - WinXP/.Net SP2
using ? unknown cc version
smoketime 2 minutes 46 seconds (average 8.300 seconds)
Summary: FAIL(m)
O = OK F =
On Sat, 17 Sep 2005, Nicholas Clark wrote:
I don't think that glibc has clean enough headers to allow perl to compile
with -ansi -pedantic on Linux - I was doing it on FreeBSD, which does.
So now I want
valgrind
dtrace
gdb that works with threads
*and*
clean system headers
I see Nicholas Clark has been hard at work integrating patches into
perl5.8.x. Trying a build on cygwin at patch 25494 passes all tests
except for op/layers.t, which should be fixed once 24764 is
integrated.
It would be nice if the version number could be bumped to 5.8.8 soon;
I inadvertently
On Mon, Sep 19, 2005 at 12:45:33PM -0700, Yitzchak Scott-Thoennes wrote:
I see Nicholas Clark has been hard at work integrating patches into
perl5.8.x. Trying a build on cygwin at patch 25494 passes all tests
except for op/layers.t, which should be fixed once 24764 is
integrated.
Ooh.
I am trying to build Perl 5.8.7 on AIX 5.2.
I can build Perl as long as I do not define use 64-bit all. If I try and
build a version with full 64-bit support I get the following error somewhere
down in the compile:
CCCMD =
cc_r -DPERL_CORE -c -D_ALL_SOURCE -D_ANSI_C_SOURCE
Nick takes the lead!
Requestors with most open tickets
Nicholas Clark40
[EMAIL PROTECTED] 39
Mark-Jason Dominus25
Stas Bekman 15
David Dyck14
[EMAIL PROTECTED] 13
Tom Christiansen 12
Dan Jacobson 9
Zefram
On Mon, Sep 19, 2005 at 01:16:34PM -0700, Robert Spier wrote:
Nick takes the lead!
Anyone would think that I programmed in Perl.
(instead of on perl)
Nicholas Clark
This Week on perl5-porters - 12-18 September 2005
Nicholas Clark announced the plan for perl 5.8.8, so it was only
fitting that someone should post a question asking how to compile
5.004. Elsewhere there continued to be lots of discussion of VMS,
carrying on from last week. All told, a
Nicholas Clark wrote:
It's the first task mentioned in the TODO for the category
Tasks that need a little C knowledge
http://public.activestate.com/cgi-bin/perlbrowse?file=pod%2Fperltodo.podrev=
(been moderately hard at work reordering the TODO to put the easier things
earlier)
Can't we just
Merijn notices this line in 5.8.x in S_new_logop
if ((type == OP_AND) == (SvTRUE(((SVOP*)first)-op_sv))) {
It's wonky. It seems to be wrong. But it's been that way since 5.8.0 started.
The corresponding point in blead is
if ((type == OP_AND SvTRUE(((SVOP*)first)-op_sv)) ||
(type ==
On Mon, 19 Sep 2005, Nicholas Clark wrote:
Merijn notices this line in 5.8.x in S_new_logop
if ((type == OP_AND) == (SvTRUE(((SVOP*)first)-op_sv))) {
It's wonky. It seems to be wrong. But it's been that way since 5.8.0 started.
The corresponding point in blead is
if ((type ==
On Fri, Sep 16, 2005 at 08:47:42PM -0400, John E. Malmberg wrote:
Anything happening with this for the 5.8.8 timeframe?
I guess I can kick 0.61 out the door.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a
On Sun, Sep 18, 2005 at 11:52:20PM -0400, John E. Malmberg wrote:
As there is no false command on VMS, this is causing rerunning a make
to fail.
Would adding the following line before the return $m be the fix for
this? Or is something else needed to make sure only the last line is
On Sep 13, 2005, at 7:53 PM, John E. Malmberg wrote:
Ken Williams wrote:
On Sep 12, 2005, at 11:12 PM, John E. Malmberg wrote:
Ken Williams wrote:
Thanks, John. I've applied your patch (in a slightly modified
form) and released a new beta, 0.13_01. It would be great if you
(and/or a
Maint is still using MakeMaker 6.17 which is now TWO YEARS OLD!
Last I checked there was some VMS failure or another possibly tied to
File::Find but I don't have details. I really rather 5.8.8 not go out with
6.17 again, 6.30 is good and stable. Can we just take the plunge, put 6.30
into
Michael G Schwern wrote:
Maint is still using MakeMaker 6.17 which is now TWO YEARS OLD!
Last I checked there was some VMS failure or another possibly tied to
File::Find but I don't have details. I really rather 5.8.8 not go out with
6.17 again, 6.30 is good and stable. Can we just take the
Rafael Garcia-Suarez wrote:
On 9/19/05, John E. Malmberg [EMAIL PROTECTED] wrote:
When I enable hard links on VMS, it exposed that the t/io/fs.t is not
testing what the comments indicate that it is testing.
The correct test would be to see if the $mode of the third link matched
the $mode for
This patch adds the ability to build Perl on 64 bit VMS V8.2 with
support for hard links, and the newer CRTL features.
Changes to configure.com:
1. Protect the link operations for the tests from someone aliasing the
link command to default for a /DEBUG build.
2. Allow override of the make
29 matches
Mail list logo
