Hi,
the attached patch solves bug #37138, that was causing perl to crash
when using an XSUB as DB::DB().
Cheers,
- Salvador
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
db_db_xsub-0.patch
Description: 2604567955-d
# New Ticket Created by Salvador Fandiño
# Please include the string: [perl #37138]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37138 >
This is a bug report for perl from [EMAIL PROTECTED]
generated with the help
Nicholas Clark wrote:
On Tue, Sep 06, 2005 at 07:01:06PM -0700, Chris Heath wrote:
Throwing an exception inside a grep sometimes causes Perl
to emit an internal warning.
$ perl -e 'for ("foo") { grep(die, "bar") }'
Died at -e line 1.
Attempt to free unreferenced scalar: SV 0x96c61dc, Perl int
Hi,
Nicholas Clark wrote:
Is there a list of the patches to blead, from which one can create a cumulative
patch representing the changes needed to add assertions.
There were not too many. Greeping for assertions on the Changes
files seems to show them all: 18727, 18735, 18739, 18750, 18827,
# New Ticket Created by Salvador Fandiño
# Please include the string: [perl #36350]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36350 >
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help
sometimes the ternary operator is parsed as the search
construction ?...? like in...
sub foo {...};
foo ? bar : doz;
And I suppose most people, like me, tends to forget about that
rare ?...? construction so lets perl be more explicit about this
possible error.
Cheers,
- Salvador
---
just another small patch for a related bug: subs with builtin
attributes shouldn't become constant subs, for instance:
$ ./perl -e 'sub foo () : assertion { 7 } ; use assertions "1"; print
foo; use assertions "0"; print foo'
77
--- ../perl-current/op.c2005-06-15 16:08:47.0 +0100
Hi,
I have been working further on the assertions support, the patch
attached provides:
- better docs
- new low level subroutines to support alternative assertion
frameworks (assertions::enabled() and assertions::seen()).
- new assertions::compat module for using assertions on perls
witho
Rafael Garcia-Suarez wrote:
Nicholas Clark wrote:
Question. What should the correct output for
$ perl -le '$r = do {local @a = 1..3; \$#a}; print $$r'
be?
Interesting question. First, observe that in maint, we have :
$ perl -le '@a = 1..2; $r = do {local @a = 1..3; \$#a}; print $$r'
0
Hi,
I reported bug #36211 via perlbug but it is not showing here
(well, here at nntp://nntp.per.org/perl.perl5.porters), and I
believe it's a serious one that shouldn't go unnoticed.
Cheers,
- Salvador.
# New Ticket Created by Salvador Fandiño
# Please include the string: [perl #36211]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36211 >
To: [EMAIL PROTECTED]
Subject: local @a inside eval
Cc: [EMAIL PROTECTED]
Reply
Hi,
When SvNV() macro is called with an SV_IV argument, it upgrades
the SV to an SV_PVNV and caches there the IV as an NV, but this
aproach can actually be counterproductive because it increases
memory usage and the processor cache performance decreases. On
the other hand, and specially, afte
> @sorted = sort { $a <=> $b } @data;
>
> uses almost twice as memory as
>
> @sorted = sort { -($a <=> $b) } @data;
>
The difference in memory usage in pp_sort is caused by elements
being stringyfied before the sorting when the comparison block is
optimized and substituted by a C function.
# New Ticket Created by Salvador Fandiño
# Please include the string: [perl #36043]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36043 >
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help
--- Yitzchak Scott-Thoennes via RT <[EMAIL PROTECTED]> wrote:
> To get qw/foo bar foo bar foo bar/, just enclose the qw// in
> parentheses:
> (qw/foo bar/ x 3).
that doesn't work either, did you meant...
(qw/foo bar/) x 3
?
cheers,
- Salvador
_
# New Ticket Created by Salvador FandiÃo
# Please include the string: [perl #35885]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35885 >
To: [EMAIL PROTECTED]
Subject: qw and x operators doesn't mix
Cc: [EMAIL PROTECTED]
# New Ticket Created by Salvador FandiÃo
# Please include the string: [perl #35884]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35884 >
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of p
# New Ticket Created by Salvador FandiÃo
# Please include the string: [perl #35878]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35878 >
To: [EMAIL PROTECTED]
Subject: goto &xsub that croaks corrupts memory
Cc: [EMAIL PR
--- Rafael Garcia-Suarez <[EMAIL PROTECTED]> wrote:
> I'm a bit worried by the fact that arbitrary regular expressions
> are allowed as an argument to the -A switch.
>
> So I think either one of those solutions must be chosen :
>
> (a) only allow things that match /(\w|,)+/ after -A (or somethin
19 matches
Mail list logo
