Michael G Schwern wrote:
The annotate command has proven very useful in tracking down historical
bits like this. Much easier than searching through old tarballs.
That's an excellent information, Michael, can this be documented
somewhere? (http://dev.perl.org/perl5/?)
You'd have to
On Mon, Dec 20, 2004 at 10:45:01AM +0100, Rafael Garcia-Suarez wrote:
That said, http://public.activestate.com/cgi-bin/perlbrowse does
blame annotation as well (with extra hyperlinks for your enhanced
experience !)
Wish List
or
Things I Can Do From SVN That I Can't Do On The Web Page
svn
Michael G Schwern wrote:
Wish List
or
Things I Can Do From SVN That I Can't Do On The Web Page
svn annotate -rX (annotate from revision X and back)
A plain annotate can only show you the last time that line was changed.
The change may have been a trivial one (subroutine moved,
On Mon, Dec 20, 2004 at 11:09:08AM +0100, Rafael Garcia-Suarez wrote:
svn diff -rX(difference between X and now)
svn diff -rX:Y (difference between X and Y)
I often use this to look for p5p applied patches to my modules since
the last time it was synced.
Michael G Schwern wrote:
On Mon, Dec 20, 2004 at 11:09:08AM +0100, Rafael Garcia-Suarez wrote:
svn diff -rX (difference between X and now)
svn diff -rX:Y(difference between X and Y)
I often use this to look for p5p applied patches to my modules since
the
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #33118]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=33118
This is a bug report for perl from [EMAIL PROTECTED],
generated with the
Stas Bekman [EMAIL PROTECTED] wrote:
:I was wondering why perlapi.pod doesn't indicate when a certain API was
:added.
I can see that this information would be useful, but it does raise some
logistical problems since it implies that when something is backported
to a maintenance release the
Automated smoke report for 5.9.2 patch 23661
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 12 hours 29 minutes (average 23 minutes 26 seconds)
Summary: FAIL(F)
O = OK F =
On Sun 19 Dec 2004 14:28, Tels [EMAIL PROTECTED] wrote:
Moin,
attached patch to include my new email. Thanx to Ilya for the nifty idea :)
Best wishes,
Thanks, address added with change #23662
Tels
--
H.Merijn BrandAmsterdam Perl Mongers (http://amsterdam.pm.org/)
using
On Mon 20 Dec 2004 01:55, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Dec 19, 2004 at 03:25:40AM -0800, Yitzchak Scott-Thoennes wrote:
What's the portability trap?
Not croaking on C stat $foo; -l _ , transferring the code to an OS where
lstat works, and only then seeing the
On Mon, Dec 20, 2004 at 05:35:12AM -0500, Michael G Schwern wrote:
svn diff -rX dir looks like it could be emulated with
find dir -type f | xargs perl -wle 'system p4 diff [EMAIL PROTECTED]
foreach @ARGV'
I don't know svn but that looks like it would just be
p4 diff dir/[EMAIL
H.Merijn Brand wrote:
On Mon 20 Dec 2004 01:55, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Dec 19, 2004 at 03:25:40AM -0800, Yitzchak Scott-Thoennes wrote:
What's the portability trap?
Not croaking on C stat $foo; -l _ , transferring the code to an OS where
lstat works,
On Sun, Dec 19, 2004 at 08:37:00PM -0500, [EMAIL PROTECTED] wrote:
Automated smoke report for 5.9.2 patch 23661
kirk: Intel(R) Celeron(R) CPU 2.00GHz (GenuineIntel 1994MHz) (i686/1 cpu)
onlinux - 2.6.8.1-12mdk [mandrake]
using cc version 3.4.1 (Mandrakelinux 10.1
On Dec 19, 2004, at 10:59 PM, Stas Bekman wrote:
I can't see what's the problem for module-authors to specify a
generation that their module works with? In fact they don't need to do
that at all since with Module::Build they can already say, that their
module requires a dependency: 1.00 =
Ken Williams wrote:
On Dec 19, 2004, at 10:59 PM, Stas Bekman wrote:
I can't see what's the problem for module-authors to specify a
generation that their module works with? In fact they don't need to do
that at all since with Module::Build they can already say, that their
module requires a
[EMAIL PROTECTED] wrote:
Stas Bekman [EMAIL PROTECTED] wrote:
:I was wondering why perlapi.pod doesn't indicate when a certain API was
:added.
I can see that this information would be useful, but it does raise some
logistical problems since it implies that when something is backported
to a
Is getting a negative reference count on an immortal a bug?
Will it actually cause problems?
$ perl -MDevel::Peek -e '$a=\(1==1); Dump !!1'
SV = PVNV(0x800e30) at 0xf6ab0
REFCNT = -2147483648
FLAGS = (IOK,NOK,POK,READONLY,pIOK,pNOK,pPOK)
IV = 1
NV = 1
PV = 0x3001b0 1\0
CUR = 1
LEN =
On Mon, Dec 20, 2004 at 03:57:48PM +0100, Rafael Garcia-Suarez [EMAIL
PROTECTED] wrote:
H.Merijn Brand wrote:
On Mon 20 Dec 2004 01:55, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Dec 19, 2004 at 03:25:40AM -0800, Yitzchak Scott-Thoennes wrote:
What's the portability trap?
On Wed, Dec 15, 2004 at 02:51:55PM +, [EMAIL PROTECTED] wrote:
I wonder whether an alternative route to fixing is to allow the deletion,
but cope with it by ensuring that variables that need to exist are
revivified when required.
I've no idea though how easy that would be to do, nor
Stas Bekman wrote:
Ken Williams wrote:
[...]
Ah, I hadn't grasped this issue. Yeah, perhaps Jos' idea of indexing
every revision on CPAN would work. It would probably be best to
create a new file (04all.index.gz?) so that the format of the existing
files doesn't change.
That's a step
Stas Bekman wrote:
That's a step forward. (Though I know Andreas is not going to like it,
because it will make the index much, much, much bigger)
Except that it shouldn't. Only those modules which have the extended
attribute (let's call it Generation for the moment) will require the
additional
On Mon, Dec 20, 2004 at 09:04:46PM +0100, Tels [EMAIL PROTECTED] wrote:
perl -wle'$a = sin(9**999); print $a; print 0+($a != 0)'
nan
1
Aha, gotcha! It should stringifiy to NaN, not nan. (To paraphrase a
dancing monkey: Consisteny! Consisteny! Consisteny! :o)
SuSv3
On Mon, Dec 20, 2004 at 10:36:23AM -0800, Yitzchak Scott-Thoennes [EMAIL
PROTECTED] wrote:
On Mon, Dec 20, 2004 at 03:57:48PM +0100, Rafael Garcia-Suarez [EMAIL
PROTECTED] wrote:
H.Merijn Brand wrote:
On Mon 20 Dec 2004 01:55, Michael G Schwern [EMAIL PROTECTED] wrote:
On Sun, Dec 19,
On Dec 20, 2004, at 4:34 PM, John Peacock wrote:
Except that it shouldn't. Only those modules which have the extended
attribute (let's call it Generation for the moment) will require the
additional index point.
Brilliant.
The reason I object to the Generation's concept is that it isn't a
Ken Williams wrote:
Yeah, that was basically my suggestion too [1], except that I preferred
to pose it as a positive assertion instead of a negative one:
backcompat_to: 2.000
Then this would work the same as the other fields like requires,
recommends, etc. - a simple number is shorthand
To start with both the suggestions form John and Ken work for me. I agree
that those are better than my original suggestion.
John Peacock wrote:
Ken Williams wrote:
Yeah, that was basically my suggestion too [1], except that I
preferred to pose it as a positive assertion instead of a negative
David Landgren wrote:
Stas Bekman wrote:
Ken Williams wrote:
[...]
Ah, I hadn't grasped this issue. Yeah, perhaps Jos' idea of indexing
every revision on CPAN would work. It would probably be best to
create a new file (04all.index.gz?) so that the format of the
existing files doesn't change.
http://www.pobox.com/~schwern/src/ExtUtils-MakeMaker-6.25_03.tar.gz
or
http://svn.schwern.org/svn/CPAN/ExtUtils-MakeMaker/trunk
or
svn://svn.schwern.org/CPAN/ExtUtils-MakeMaker/trunk
or
a CPAN mirror near you.
6.26 release candidate.
This alpha release overhauls the blibdirs generation yet again
28 matches
Mail list logo
