autouse.pm: check stub, use goto in stub

2005-08-17 Thread Alexey Tourbin
Hello, $ perl -e 'use autouse Pod::Usage => "pod2usage(()"; pod2usage()' Undefined subroutine &main::pod2usage called at -e line 1. $ --- autouse.pm- 2004-07-04 21:32:39 + +++ autouse.pm 2005-08-18 05:01:52 + @@ -63,7 +62,8 @@ sub import { }; if (defined $proto) { -

autouse.pm: remove unneeded eval

2005-08-17 Thread Alexey Tourbin
Hello, $ perl -le 'use autouse qw(asdf zxcv); zxcv()' Can't locate asdf.pm in @INC (@INC contains: [skip] .) at /usr/lib/perl5/autouse.pm line 53. ...propagated at /usr/lib/perl5/autouse.pm line 54. $ --- autouse.pm- 2004-07-04 21:32:39 + +++ autouse.pm 2005-08-18 04:08:19 + @@

Re: resolving methods at compile time

2005-08-17 Thread Dave Mitchell
On Wed, Aug 17, 2005 at 03:37:13PM -0500, David Nicol wrote: > which could also AIUI benefit /slightly/ from binding the subroutine's > entry point directly to the node that calls it instead of looking the > entry point up in a hash, This would not work. The same sub entry op may call many differe

Re: resolving methods at compile time

2005-08-17 Thread Yuval Kogman
On Wed, Aug 17, 2005 at 12:19:25 -0700, Jan Dubois wrote: > All of this is dead now, so I don't think type annotation serves any > useful purpose anymore at all. No no no! 'use fields' is there so that it can *retain* compatibility and usefulness even when pseudohashes go out the door! 5.9's fi

Re: resolving methods at compile time

2005-08-17 Thread David Nicol
On 8/17/05, Rick Delaney <[EMAIL PROTECTED]> wrote: > > As for speeding up method lookups, aren't they cached after the first > lookup anyway? Isn't the slowness of method calls simply the slowness > of subroutine calls? which could also AIUI benefit /slightly/ from binding the subroutine's ent

Re: resolving methods at compile time

2005-08-17 Thread Rick Delaney
On Wed, Aug 17, 2005 at 12:19:25PM -0700, Jan Dubois wrote: > > I thing the "type annotation" syntax was only used for the pseudohash > support in fields.pm. E.g. you could write: > > my Type $self = shift; > $self->{foo} = 1; > > and if Type didn't have a field "foo" you would get a co

RE: resolving methods at compile time

2005-08-17 Thread Jan Dubois
On Wed, 17 Aug 2005, Stas Bekman wrote: > > A few years ago Doug MacEachern started to write code like: > >my Apache2::Connection $c = shift; >$c->foo; # should be already resolved > > i.e. adding an explicit class name before the object. If I remember > correctly he was saying that perl

Re: resolving methods at compile time

2005-08-17 Thread Dave Mitchell
On Wed, Aug 17, 2005 at 11:44:11AM -0700, Stas Bekman wrote: > but what's the answer for my question? Does that declaration just gets > ignored? A quick look at bleed src indicates that is only used to provide a stash name when calling attribute handlers, ie in my Stash $foo : attributes; -

Re: resolving methods at compile time

2005-08-17 Thread Stas Bekman
Fergal Daly wrote: One problem was that if you pass in something which inherits from Apache2::Connection you'd expect it to work. However if the object overrides foo() it will be ignored, which is probably not what you want to happen. A bit like static methods in C++, Thanks Fergal, but what's

resolving methods at compile time

2005-08-17 Thread Stas Bekman
A few years ago Doug MacEachern started to write code like: my Apache2::Connection $c = shift; $c->foo; # should be already resolved i.e. adding an explicit class name before the object. If I remember correctly he was saying that perl was supposed to optimise method lookups at compile-time

Re: [perl #36928] invalid utf8 causes hand on regex match

2005-08-17 Thread Dave Rolsky
ECANNOTSPELL! The subject should say "causes hang", not "causes hand" ;) -dave /*=== VegGuide.Orgwww.BookIRead.com Your guide to all that's veg. My book blog ===*/

Re: [perl #36903] Regular expression causes segfault

2005-08-17 Thread Milo Thurston
In message <[EMAIL PROTECTED]> you wrote: >In this case, I believe the recursion is caused by your use of the >cut operator /(?>...)/, so you may be able to work around the problem >by recasting the regexp to avoid this; in general, though, only the >simplest regexp can be sure to avoid the problem

Re: Ping? [PATCH] Re: [perl #36654] Inconsistent treatment of NaN

2005-08-17 Thread Rafael Garcia-Suarez
Yitzchak Scott-Thoennes wrote: > Can the patches in: > http://nntp.perl.org/group/perl.perl5.porters/103801 > and > http://nntp.perl.org/group/perl.perl5.porters/103906 > > be applied (or receive feedback)? Thanks. Thanks, both have been applied as change #25299.

Smoke [5.9.3] 25296 FAIL(XF) bsd/os 4.1 (i386/1 cpu)

2005-08-17 Thread kane
Automated smoke report for 5.9.3 patch 25296 fixit.xs4all.nl: Pentium II (i386/1 cpu) onbsd/os - 4.1 using cc version egcs-2.91.66 19990314 (egcs-1.1.2 release) smoketime 3 hours 55 minutes (average 1 hour 57 minutes) Summary: FAIL(XF) O = OK F = Failure(s), extended repo

Re: segfault while DELETE THIS

2005-08-17 Thread Nicholas Clark
On Thu, Aug 11, 2005 at 11:55:49AM +0800, Dongxu Ma wrote: > According to typemap in ExtUtils and perl.h, casting IV to pointer > should be safe in this case, since on my machine(32bit, kernel > 2.6.12), sizeof(int) == 4, which is the same as a pointer. Does > anyone have any idea about this issu

Re: Ping? [PATCH] Re: [perl #36654] Inconsistent treatment of NaN

2005-08-17 Thread Yitzchak Scott-Thoennes
On Wed, Aug 17, 2005 at 04:15:56PM +1000, Sisyphus wrote: > > - Original Message - > From: "Yitzchak Scott-Thoennes via RT" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 17, 2005 2:24 PM > Subject: Ping? [PATCH] Re: [perl #36654] Inconsistent treatment of NaN >

Re: Ping? [PATCH] Re: [perl #36654] Inconsistent treatment of NaN

2005-08-17 Thread Sisyphus
- Original Message - From: "Yitzchak Scott-Thoennes via RT" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 17, 2005 2:24 PM Subject: Ping? [PATCH] Re: [perl #36654] Inconsistent treatment of NaN > Can the patches in: > http://nntp.perl.org/group/perl.perl5.porters

Smoke [5.9.0] 25296 FAIL(m) openbsd 3.6 (i386/1 cpu)

2005-08-17 Thread Steven P. Schubiger
Automated smoke report for 5.9.0 patch 25296 accognoscere.homeunix.org: AMD Athlon(TM) XP 1800+ ("AuthenticAMD" 686-class) (i386/1 cpu) onopenbsd - 3.6 using cc version 2.95.3 20010125 (prerelease, propolice) smoketime 3 minutes 1 seconds (average 22.625 seconds) Summary:

[perl #36928] invalid utf8 causes hand on regex match

2005-08-17 Thread via RT
# New Ticket Created by Dave Rolsky # Please include the string: [perl #36928] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=36928 > This is a bug report for perl from [EMAIL PROTECTED], generated with the help of perlbu

RE: [perl #36839] \xA0 (non-breaking space) does and doesn't matc h \s

2005-08-17 Thread Konovalov, Vadim
> Konovalov, Vadim wrote: > > > However, this is *the* unfixable UTF-8 bug in Perl 5 - the > > > fact that 1 bit > > > is used as a flag that both signals "buffer is encoded as > UTF-8" and > > > "string should use Unicode rather than bytes semantics" > > > > But may be those two concepts shoul

Smoke [5.9.3] 25296 FAIL(F) MSWin32 WinXP/.Net SP2 (x86/2 cpu)

2005-08-17 Thread Steve Hay
Automated smoke report for 5.9.3 patch 25296 Mugwump.uk.radan.com: Intel(R) Pentium(R) 4 CPU 3.40GHz(~3391 MHz) (x86/2 cpu) onMSWin32 - WinXP/.Net SP2 using cl version 12.00.8804 smoketime 10 hours 18 minutes (average 15 minutes 28 seconds) Summary: FAIL(F) O = OK F = Fa