Andy Lester <[EMAIL PROTECTED]> writes:
> Also, it apparently uses POD as an intermediate file conversion format
> for its docs during the build process.
Yup, I've worked with several of the GNU maintainers on this. They don't
want to maintain separate man pages, so they have a script that conve
I compiled up perl-current under gcc 4.1 (20050409 version) to see what
turns up. It's a lot pickier about casting, especially pointer types.
If anyone's interested in the warnings it throws, let me know. I
haven't dug into what new warnings are available.
Also, it apparently uses POD as an
On Wed, Apr 13, 2005 at 08:48:35PM -0500, Andy Lester ([EMAIL PROTECTED]) wrote:
> I will adjust accordingly, and also make a patch with that as a test
> case.
Updated patch, plus added a test case to t/op/concat.t.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
-
Find a test case.
That much I knew. I am familiar with this "test" idea.
perl -wle'$x=eval"qr/\x{fff}/"; print ord chop($x .= "\303\277")'
should print 191. I suspect that with Andy's patch it will print 255.
Later: it does print 255.
I will adjust accordingly, and also make a patch with that as
On Wed, Apr 13, 2005 at 09:13:16PM +, Ton Hospel wrote:
> In article <[EMAIL PROTECTED]>,
> Andy Lester <[EMAIL PROTECTED]> writes:
> > On Tue, Apr 12, 2005 at 10:26:58PM -0700, Yitzchak Scott-Thoennes ([EMAIL
> > PROTECTED]) wrote:
> >> That SvPV_nomg may be needed to set the UTF8 flag.
On Wed, Apr 13, 2005 at 10:10:10PM +0100, Nick Ing-Simmons wrote:
> >+local *STDIN = IO::Handle->new_from_fd(0, 'r') unless fileno(STDIN)
> >== 0;
> >+local *STDOUT = IO::Handle->new_from_fd(1, 'w') unless fileno(STDOUT)
> >== 1;
>
> I assume that has been tested. It looks worryingly l
# New Ticket Created by Raphael Wegmann
# Please include the string: [perl #34968]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34968 >
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of pe
On Wed, Apr 13, 2005 at 10:18:44PM +0100, Nick Ing-Simmons wrote:
> >>From regen_perly.pl:
> >
> > # Note that perly.c is *not* regenerated - this is now a static file which
> > # is not dependent on perly.y any more.
>
> It is still generated (by pumpkings) - perl's grammar is hard enough
> to
Marcus Holland-Moritz <[EMAIL PROTECTED]> writes:
>On 2005-04-13, at 14:47:11 -0500, Graham Barr wrote:
>
>> Although perly.c is shipped in the tarball, it is actually generated.
>
>>From regen_perly.pl:
>
> # Note that perly.c is *not* regenerated - this is now a static file which
> # is not dep
In article <[EMAIL PROTECTED]>,
Steven P Schubiger <[EMAIL PROTECTED]> writes:
> --- lib/IO/Pipe.pmSun Apr 4 15:32:35 2004
> +++ lib/IO/Pipe.pmWed Apr 13 05:38:32 2005
> @@ -51,6 +51,8 @@
> }
> elsif(defined $pid) { # Child or spawn
> my $fh;
> + local *STDIN
Andy Lester <[EMAIL PROTECTED]> writes:
>Looks to me like yydestruct() in perly.c is an artifact created by bison
>long ago,
Until someone touches perly.y again.
Don't patch perly.c patch the thing that patches it ;-)
>but never removed. It does nothing, and yet is called
>multiple times. It'
In article <[EMAIL PROTECTED]>,
Andy Lester <[EMAIL PROTECTED]> writes:
> On Tue, Apr 12, 2005 at 10:26:58PM -0700, Yitzchak Scott-Thoennes ([EMAIL
> PROTECTED]) wrote:
>> That SvPV_nomg may be needed to set the UTF8 flag.
>
> So how do we know? And can we make it explicit? I would thin
Steven P Schubiger <[EMAIL PROTECTED]> writes:
>On 12 Apr, Zefram wrote:
>
>: The ->writer and ->reader methods on IO::Pipe rely on STDIN and STDOUT
>: (respectively) being attached to the usual file descriptors. If they
>: are not, then the child process ends up with its end of the pipe attached
Gurusamy Sarathy <[EMAIL PROTECTED]> writes:
>
>Incidentally, I see this in 5.8.6's PerlIOStdio_invalidate_fileno():
>
>#if 0
> /* Sarathy's code did this - we fall back to a dup/dup2 hack
> (which isn't thread safe) instead
>*/
>#error "Don't know how to set FILE
Bstrand @ Switchmanagement . Com writes:
># New Ticket Created by [EMAIL PROTECTED]
># Please include the string: [perl #34934]
># in the subject line of all future correspondence about this issue.
># https://rt.perl.org/rt3/Ticket/Display.html?id=34934 >
>
>
>
>This is a bug report for perl f
On 2005-04-13, at 14:47:11 -0500, Graham Barr wrote:
> Although perly.c is shipped in the tarball, it is actually generated.
From regen_perly.pl:
# Note that perly.c is *not* regenerated - this is now a static file which
# is not dependent on perly.y any more.
Marcus
--
Computers are usel
On Wed, April 13, 2005 10:06 am, Andy Lester said:
> Looks to me like yydestruct() in perly.c is an artifact created by bison
> long ago, but never removed. It does nothing, and yet is called
> multiple times. It's static, and the string "yydestruct" appears
> nowhere else in the tree. Looks lik
On Wed, Apr 13, 2005 at 09:21:48AM +0100, Steve Hay wrote:
> Michael G Schwern wrote:
>
> >http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.28.tar.gz
> >
> Any ideas how to fix the current problems in bleadperl on Win32?:
> http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-04/msg00
On Wed, 13 Apr 2005 11:59:08 -0700, Yitzchak Scott-Thoennes <[EMAIL PROTECTED]>
wrote:
> On Wed, Apr 13, 2005 at 10:11:52AM +0200, Rafael Garcia-Suarez wrote:
> > I don't reproduce these; maybe related to setting
> > $Test::Harness::Switches = '"-Mstrict"';
> > in this test (and thus the sympt
On Wed, Apr 13, 2005 at 10:11:52AM +0200, Rafael Garcia-Suarez wrote:
> I don't reproduce these; maybe related to setting
> $Test::Harness::Switches = '"-Mstrict"';
> in this test (and thus the symptom of a more general problem
> about running perl with the correct environment ?)
Hmm; the fa
On Tue, Apr 12, 2005 at 03:55:40PM +0100, Nicholas Clark wrote:
> It looks like it's a more fundamental problem of where the overloading flag
> is stored:
>
> To make things work, it needs to be on the referent, not the reference.
I'm not sure there's a flag available on every type of referent, w
On Wed, 13 Apr 2005, Parashkev Penev wrote:
> # New Ticket Created by Parashkev Penev
> # Please include the string: [perl #34953]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=34953 >
> I tried to compile perl 5.8.5
On Wed, 13 Apr 2005 10:06:47 -0500, Andy Lester <[EMAIL PROTECTED]> wrote:
> Looks to me like yydestruct() in perly.c is an artifact created by bison
> long ago, but never removed. It does nothing, and yet is called
> multiple times. It's static, and the string "yydestruct" appears
> nowhere els
Hi,
Von "Gurusamy Sarathy via RT" <[EMAIL PROTECTED]> (13 Apr 2005 02:17:50 -):
> On Tue, 12 Apr 2005 10:35:51 +0200, "Dagobert Michelsen" wrote:
> >Von "Gurusamy Sarathy via RT" <[EMAIL PROTECTED]> (12 Apr 2005 03:26:4
> >2 -):
> >> I remember fixing a problem similar to the one you've re
Looks to me like yydestruct() in perly.c is an artifact created by bison
long ago, but never removed. It does nothing, and yet is called
multiple times. It's static, and the string "yydestruct" appears
nowhere else in the tree. Looks like it's safe to yank.
Plus the usual consting, of course.
On Tue, Apr 12, 2005 at 10:26:58PM -0700, Yitzchak Scott-Thoennes ([EMAIL
PROTECTED]) wrote:
> That SvPV_nomg may be needed to set the UTF8 flag.
So how do we know? And can we make it explicit? I would think some
test somewhere in the UTF8 stuff would have failed.
--
Andy Lester => [EMAIL PRO
On 13 Apr 2005 10:20:58 -, Parashkev Penev (via RT)
<[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Parashkev Penev
> # Please include the string: [perl #34953]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=34
# New Ticket Created by Parashkev Penev
# Please include the string: [perl #34953]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34953 >
Hi to all perl developers out there
I tried to compile perl 5.8.5 on my computer. c
Yitzchak Scott-Thoennes wrote:
> These failures just started recently, perhaps having been masked
> before by the 5.9.2 I had installed.
>
> lib/Test/Harness/t/strap-analyze..Can't locate if.pm in @INC (@INC
> contains: /usr/local/lib/perl5/5.9.3/cygwin-thread-multi-64int
> /usr/local/li
On 12 Apr, Zefram wrote:
: The ->writer and ->reader methods on IO::Pipe rely on STDIN and STDOUT
: (respectively) being attached to the usual file descriptors. If they
: are not, then the child process ends up with its end of the pipe attached
: to the wrong file descriptor. Example:
:
: $ ech
Automated smoke report for 5.9.3 patch 24231
TANGAROA.uk.radan.com: Intel(R) Pentium(R) 4 CPU 2.00GHz(~1992 MHz) (x86/1 cpu)
onMSWin32 - WinXP/.Net SP1
using cl version 12.00.8804
smoketime 11 hours 6 minutes (average 20 minutes 50 seconds)
Summary: FAIL(F)
O = OK F = Fa
Robin Barker wrote:
> This is a patch against perl-5.9.2 to deal with -Wformat warnings.
Thanks, applied as change #24233 to bleadperl.
Michael G Schwern wrote:
>http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.28.tar.gz
>
Any ideas how to fix the current problems in bleadperl on Win32?:
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-04/msg00216.html
The problems seem to have crept in in version 6.25_07: If I
33 matches
Mail list logo
