At 6:43 PM +0200 10/26/04, Abe Timmerman wrote:
Automated smoke report for 5.8.5 patch 23415
FAFNER: VAX_7000-720 (VAX_7000-720/2 cpu)
onopenvms - V7.2
using CC/DECC version 60490005
smoketime 5 hours 4 minutes (average 5 hours 4 minutes)
Congratulations, and thanks for
Anders Johnson wrote:
Perhaps I'm the only person in the world who cares that Perl can't do
this, but that proposition seems at odds with the widespread use of RAII
in languages that support it.
I was actually just thinking tonight about how to implement RAII in
Perl, I did some google
Hi,
I wonder what people think about the idea of adding a third argument to
File::Copy::move(). I'd like to be able to pass a code-reference that
gets triggered after each copying of a block.
Background: I am using File::Copy in a program where I regularly have to
poll an object (used for
On Fri, Oct 22, 2004 at 02:27:31PM -0400, Michael G Schwern wrote:
On Fri, Oct 22, 2004 at 05:43:06PM -, Steve Peters via RT wrote:
$ perldoc -f =
No documentation for perl function `=' found
... = [is an] operator, not a function, and therefore
not returned by perldoc -f. This is
On Wed, Oct 27, 2004 at 08:56:36AM +0200, Tassilo von Parseval wrote:
I wonder what people think about the idea of adding a third argument to
File::Copy::move(). I'd like to be able to pass a code-reference that
gets triggered after each copying of a block.
Background: I am using File::Copy
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #32154]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32154
The getXXXent PERL functions (e.g. getgrent) use getXXXent_r (e.g.
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #32163]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32163
This is a bug report for perl from [EMAIL PROTECTED],
generated with the
Mmm, thinking a bit more about the optimization to only have one version
of a sub leads me to the following, which I think should be considered
a bug, not just an unexpected optimization:
#!/usr/bin/perl -lw
sub foo {
bless sub {}, shift;
}
my $a = foo(A);
print a is now a , ref($a);
On Wed, Oct 27, 2004 at 09:52:15AM +, Ton Hospel [EMAIL PROTECTED] wrote:
Mmm, thinking a bit more about the optimization to only have one version
of a sub leads me to the following, which I think should be considered
a bug, not just an unexpected optimization:
Yes, this has been
On Wed, Oct 27, 2004 at 09:48:32AM +0100, David Cantrell [EMAIL PROTECTED] wrote:
On Fri, Oct 22, 2004 at 02:27:31PM -0400, Michael G Schwern wrote:
On Fri, Oct 22, 2004 at 05:43:06PM -, Steve Peters via RT wrote:
$ perldoc -f =
No documentation for perl function `=' found
... =
On Wed, Oct 27, 2004 at 04:49:27AM -0400 Michael G Schwern wrote:
On Wed, Oct 27, 2004 at 08:56:36AM +0200, Tassilo von Parseval wrote:
I wonder what people think about the idea of adding a third argument to
File::Copy::move(). I'd like to be able to pass a code-reference that
gets
I wonder what people think about the idea of adding a
third argument to
File::Copy::move(). I'd like to be able to pass a
code-reference that
gets triggered after each copying of a block.
Background: I am using File::Copy in a program where I
regularly have to
poll an
On Wed 27 Oct 2004 13:47, Tassilo von Parseval [EMAIL PROTECTED] wrote:
On Wed, Oct 27, 2004 at 04:49:27AM -0400 Michael G Schwern wrote:
On Wed, Oct 27, 2004 at 08:56:36AM +0200, Tassilo von Parseval wrote:
I wonder what people think about the idea of adding a third argument to
On Wed, Oct 27, 2004 at 01:47:46PM +0200, Tassilo von Parseval wrote:
None of this is desirable or even possible for a number of reasons. I
suggested modifying File::Copy::move() for a reason: It's hardly
acceptable that there is a function that - depending on its parameters -
could block
At 2004-10-26 23:32:25 -0500, [EMAIL PROTECTED] wrote:
--- lib/Carp.t;-0 Tue Aug 17 03:50:24 2004
+++ lib/Carp.tTue Oct 26 23:02:45 2004
Thanks, applied. (#23425)
-- ams
Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote:
:On Wed, Oct 27, 2004 at 09:48:32AM +0100, David Cantrell [EMAIL PROTECTED] wrote:
: On Fri, Oct 22, 2004 at 02:27:31PM -0400, Michael G Schwern wrote:
: On Fri, Oct 22, 2004 at 05:43:06PM -, Steve Peters via RT wrote:
:$ perldoc -f =
:
On Wed, Oct 27, 2004 at 01:47:46PM +0200, Tassilo von Parseval wrote:
None of this is desirable or even possible for a number of reasons. I
suggested modifying File::Copy::move() for a reason: It's hardly
acceptable that there is a function that - depending on its parameters -
could block
Perl is going into an infinite loop. The following bt was repeated
again and again in my core file.
#0 Perl_amagic_call (left=0xaa302a8, right=0x8146914, method=4, flags=9)
at gv.c:1463
#1 0x080c70f5 in Perl_sv_2pv_flags (sv=0xaa302a8, lp=0xbf80016c, flags=2)
at sv.c:3634
#2
trie optimization for regexp groups means optimizing things like
m/(flash|flat|flatulent|flabby)\b/
into things like
m/fla(sh|bby|(t(|ulent)))\b/
right?
I wonder if it would be possible to do it with a regex preprocessor.
On Tue, 26 Oct 2004 11:49:13 +0100, Nicholas Clark
Steve Peters wrote:
On Friday 22 October 2004 11:24 am, Stas Bekman wrote:
It looks like we have a bug in qr//m in all perls. Here is a test case:
[...]
Going through some old perlbugs, there are at least two old bugs mentioning
this problem. Perlbug #3038
As some of you may know, compling perl with DEBUG_LEAKING_SCALARS
causes the addresses of all leaked scalars to be printed at
cleanup time. The change below makes it print out the sv_flags and
sv_refcnt fields too.
That's one small step for a man ... or something.
Dave.
--
Counsellor Troi
On Wednesday 27 October 2004 03:17 pm, David Nicol wrote:
trie optimization for regexp groups means optimizing things like
m/(flash|flat|flatulent|flabby)\b/
into things like
m/fla(sh|bby|(t(|ulent)))\b/
right?
I wonder if it would be possible to do it with a regex
I'll need to revise my below post. On doing additional searching, I
found a patch in late 2000 that supposedly makes DESTROY deterministic
as provided in the following example.
http://www.perl.com/pub/a/2000/12/p5pdigest/THISWEEK-20001210.html
sub x::DESTROY {print shift-[0]}
{ my $a1 =
23 matches
Mail list logo
