SADAHIRO Tomoyuki wrote:
perl5 porters,
There is a response in approval from Sastry to my proposed patch.
I'll forward it and now submit the proposal (on my prev mail) to p5p.
Thanks, applied as change #25303 to bleadperl.
[EMAIL PROTECTED] wrote:
The 5.9.x patch is against the patch level 25301, and contains minor
const-change
induced changes, plus adding Compress::Zlib to the set of supported extensions
(also adding IO::Zlib).
Thanks, applied as #25304 to bleadperl; including the C::Zlib changes.
Note the
YAMASHINA Hio wrote:
I build perl with icc9, but got message some tests failed.
hints/linux.sh cannot detect icc9 as icc.
diff -urN perl-5.8.7.orig/hints/linux.sh perl-5.8.7/hints/linux.sh
--- perl-5.8.7.orig/hints/linux.sh 2005-04-05 05:08:31.0 +0900
+++
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.
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 should be considered synonyms in
Dominic Dunlop (via RT) wrote:
The following is seen in a debugging [EMAIL PROTECTED], but not in a
debugging
perl5.8.7:
$ ./perl -Ilib -Dx -MConfig -e 1 # or -Mstrict, or ...
Thanks, fixed by change #25296.
[...]
Segmentation fault
On 8/9/05, Alexey Tourbin [EMAIL PROTECTED] wrote:
Okay. My concern is that bugfix changes are not tagged as bufixes (at
least as they come through perl5-changes), so there's a chance you can
miss the one when there's a lot of them.
I should get more verbose in my application logs...
(Being
On 8/8/05, David Nicol [EMAIL PROTECTED] wrote:
On 8/8/05, Nicholas Clark [EMAIL PROTECTED] wrote:
On Wed, Aug 03, 2005 at 06:04:44PM -0700, Michael G Schwern wrote:
On Thu, Aug 04, 2005 at 12:26:32AM +0200, Abigail wrote:
What would the gain be if you remove $[?
Taking it out would
On 8/6/05, Jarkko Hietaniemi [EMAIL PROTECTED] wrote:
How is the fixing of lexical pragmas progressing? If there were
a working solution for that, I could implement a pragma for shifting
of scalars as bitvecs.
I've an unfinished patch, and I've planned to work on this after the
next 5.9.x
On 8/5/05, Dan Kogai [EMAIL PROTECTED] wrote:
I decided to finish my homework before I leave Portland. That is,
Encode-2.11.
Thanks, applied (with the PerlIO::encoding patch) as #25271.
Although you missed this chunk from bleadperl :
--- ext/Encode/encoding.pm (révision 19732)
+++
On 8/5/05, Tassilo von Parseval [EMAIL PROTECTED] wrote:
just a minor correction for perldiag.pod.
Thanks, applied.
Other than that, this 'thread failed to start' warning is really hard to
get rid of. Should any of the warnings in perldiag.pod be immune to even
the -X switch, as this one is?
On 8/2/05, John E. Malmberg [EMAIL PROTECTED] wrote:
This bug is in the routine mp_to_vmsspec(). If it is passed a name like
/foo where foo is a logical name, with no other directories or file
names in the path, after the translation, the null terminator was always
being skipped over, and
On 8/4/05, Abigail [EMAIL PROTECTED] wrote:
What would the gain be if you remove $[?
Only internal gains. Mostly memory improvements, since each control OP
in the optree stores $[ on 32 bytes currently. Also, probably
unnoticeable speed improvements (bug integer addition isn't that
expensive.)
On 8/3/05, Ivan Tubert-Brohman [EMAIL PROTECTED] wrote:
perldata says:
Version 5 of Perl changed the semantics of $[: files that don't set the
value of $[ no longer need to worry about whether another file changed
its value. (In other words, use of $[ is ***deprecated***.)
In other words,
John E. Malmberg wrote:
This test is exiting before running any tests with an undefined value
being referenced if $Config{u64size} is not defined.
Thanks, applied as change #25249.
John E. Malmberg wrote:
The script 03examples.t is failing at test 1 because the includes seem
to be set wrong for VMS.
--- ext/compress/zlib/t/03examples_t.blead Sun Jul 31 22:54:06 2005
+++ ext/compress/zlib/t/03examples.tSun Jul 31 22:54:12 2005
@@ -42,7 +42,7 @@
my $Inc =
John E. Malmberg wrote:
This requires fixing in multiple places.
perl.h, util.c, and embed.fnc, and this seems to require a running perl
to rebuild proto.h
Thanks, applied as change #25251.
Michael G Schwern wrote:
Bleadperl appears to have this fixed. A test is attached. Ironically
the fresh_perl test function would always append a newline to the code
being tested. I've whacked that out, it was a hold over from the original
code in t/run/kill_perl.t.
Thanks, applied as
Piotr Fusik wrote:
I've extracted a list of words from all the PODs and spell-checked it.
The result is in the attachment.
Thanks, applied, except bits that touch dual-live modules.
I didn't apply the bit to perltoc.pod, which is a generated document,
and I backported the bit to perlapi.pod to
This patch adds 2 cpp symbols to be checked by Configure for linux/gcc on
AMD64.
--- Configure (révision 5520)
+++ Configure (copie de travail)
@@ -19995,7 +19995,7 @@
$cat 'EOSH' Cppsym.know
a29k ABI64 aegis AES_SOURCE AIX AIX32 AIX370
AIX41 AIX42 AIX43 AIX_SOURCE aixpc ALL_SOURCE
Paul Marquess wrote:
- $Inc = '-I[.blib.lib] -I[.blib.arch]';
+ $Inc = '-I[-.lib] -I[-.arch]';
}
elsif ($^O eq 'MSWin32') {
foreach (@INC)
Is this the layout needed for running these tests when Compress::Zlib is in
the core only? Is the use of blib still valid for the case
John E. Malmberg wrote:
The existing code in the fopen() call aways fails with an invalid
argument, so the if clause following it has never been run since this
version of the code was in place.
Fixing this bug may expose other side effects as it is assuming that the
first 4 bytes of an
John E. Malmberg wrote:
Change #25218 needs to be backed out. Adding the (char *) cast to
suppress a the compiler warning changes a build time error in to several
potential run time errors, including access violations and data corruptions.
Patch 25217, while making the code build, has
Michael G Schwern wrote:
So it sounds like the resolution for this bug is to document that sort
uses aliases like grep does. I've stolen the wording from grep.
Thanks, applied as change #25258.
Andy Lester wrote:
In Simon's Advanced Perl Programming, 2e there's a quote from
overload.pm that warrants a [sic]. This fixed that.
Thanks applied, with a nit :
+It is possible to hook into this process via Coverload::constant()
+and Coverload::remove_constant() functions.
I added a the
Andy Lester wrote:
* embed.fnc: Adding many NN and NULLOK flags. I'm down to 280 or so
pointer parameters to clean up. In at least one case, I fixed one that
was wrong (force_list).
* doio.c: Consting
* op.c: Fixed some indents. Hoisted a check for non-null outside of an
if-then
Piotr Fusik wrote:
$ perl -we '-o'
Use of uninitialized value in -O at -e line 1.
$ perl -we '-O'
Use of uninitialized value in -o at -e line 1.
I have no idea if anything other than warnings can be affected by this bug.
A patch is attached.
Thanks, applied, as #25232, except the
Piotr Fusik wrote:
No characters should be allowed in a subroutine prototype
after an '@' (but not '\@'). This is because no arguments
and not in a [].
can be effectively passed to a subroutine after an array argument.
I insist on an error, but a warning would be better than nothing.
One
H.Merijn Brand wrote:
say, it sounds like a Skip for HP-UX 10.20. However, sprintf.t
currently says:
# we do not load %Config since this test resides in op and needs
# to run under the minitest target even without Config.pm working.
Raphael ruled that removing the comment and using
Robin Barker wrote:
This fixes some compiler warnings in mg.c and POSIX.xs,
and clarifies some related macro definitions in perl.h
Thanks, applied as #25236.
Robin Barker wrote:
This patch changes my previous patch 25171
to use STRINGIFY instead of #n.
config.h defines CAT2 and STRINGIFY:
STRINGIFY(n) is used (instead of #n),
but CAT2 is rarely used (instead of ##).
Does this matter? I guess not.
Thanks, applied as change #25238.
Michael G Schwern wrote:
Removing the auto-newline appending in fresh_perl_is() exposed some newline
sloppiness in t/run/fresh_perl.t.
* When switches were stripped from test code a blank line was left.
This confused attempts by fresh_perl to display the first line of the
program as a
Green, Paul wrote:
My weekly build of bleedperl failed last night:
mg.c: In function `Perl_sighandler':
mg.c:2715: structure has no member named `si_errno'
I tracked it down to the sa_siginfo changes.
Stratus VOS implements the 1996 revision of the POSIX standard. That
version defines
On 7/24/05, Piotr Fusik [EMAIL PROTECTED] wrote:
--- perl-current/pod/perlfunc.pod Sun Jul 24 11:30:36 2005
+++ perl-patched/pod/perlfunc.pod Sun Jul 24 11:38:16 2005
Thanks, applied as change #25241.
John W. Krahn wrote:
--- perlfunc.pod2005-04-01 01:43:07.0 -0800
+++ /home/john/5.9.2-perlfunc.pod 2005-07-26 00:43:00.0 -0700
@@ -226,7 +226,7 @@
Cendnetent, Cendprotoent, Cendpwent, Cendservent, Cexec,
Cfcntl, Cflock, Cfork, Cgetgrent, Cgetgrgid,
Brezovec, Dick wrote:
You may give one or more space-separated answers, or none if appropriate.
A well-behaved OS will have no hints, so answering none or just Policy
is a good thing. DO NOT give a wrong version or a wrong OS.
Which of these apply, if any? [solaris_2] solaris_8
On 7/24/05, Michael G Schwern [EMAIL PROTECTED] wrote:
More importantly for the purposes of documentation, at least on my system,
I see this:
Just because someone else does something poorly doesn't mean we have to, too.
perlfunc says :
=item crypt PLAINTEXT,SALT
Encrypts a string exactly
H.Merijn Brand wrote:
I've applied Jarkko's `fix' for POSIX machines not being POSIX after all on
signals, and I have extended Steve Hay's patch 25209:
Change 25210 on 2005/07/21 by [EMAIL PROTECTED] 'I *DO* have AIX, and
extending '
Change 25209 on 2005/07/21 by [EMAIL PROTECTED] 'Make
Michael G Schwern (via RT) wrote:
I think its more correct to say
Yes. Thanks, applied as #25213.
Steve Hay wrote:
The reason is that miniperl was built without ithreads (hence it is
correctly not in Compile-time options), but perl was built with
ithreads, so lib/Config_heavy.pl contains useithreads='define', which
miniperl uses too!
Looking at the makefiles, I see that this can
Paul Marquess wrote:
The primary purpose of this patch is to update the private copy of zlib to
1.2.3. See Changes for the rest.
Standalone version has just been uploaded to CPAN.
Thanks, applied as change #25205.
Jarkko Hietaniemi wrote:
As suggested by Andy Dougherty.
Thanks, applied as #25191.
On 7/14/05, Robin Barker [EMAIL PROTECTED] wrote:
I suggest we use this patch I proposed earlier (as one of two alternatives).
It removes mv-if-diff from lib/Config.pm and uses lib/Config.pod to
de-parallelise the call to configpm. There does not seem much downside to
this approach --
Tassilo von Parseval wrote:
Hi,
the attached proposed patch against blead hopefully fixes a problem when
a lvalue-sub has an element of a tied hash or array as its last
statement. It should be a solution for buglet #30582 Conflicts between
the :shared attribute and lvalue subroutines which
Nicholas Clark wrote:
On Thu, Jun 23, 2005 at 11:49:14PM +0200, Rafael Garcia-Suarez wrote:
I can't detect any :unique in blead modules.
The only one I know of is our $summary : unique in Config_heavy.pl
Removed as change #25195 in blead.
So that's a big plus for removing it (which
Stas Bekman wrote:
someone has broken croak(Nullch) in blead:
modperl_error.c: In function `modperl_croak':
modperl_error.c:93: warning: null argument where non-null required (arg 2)
which shouldn't happen, since it's a documented feature:
That should be fixed by change #25197, thanks.
Jarkko Hietaniemi wrote:
Now to followup on my own patch of two years ago [1], here is support
for SA_SIGINFO (see man sigaction), which allows additional information
to be passed on to the signal handlers (beyond the signal number).
Here's the patch.
Thanks, applied as #25200.
Steve Hay wrote:
Line 544 in pad.c
if (off = PL_comppad_name_floor)
causes a signed/unsigned mismatch on Win32 using VC++.
off is a PADOFFSET (an unsigned type), while PL_comppad_name_floor is an
I32 (a signed type).
Which is the correct fix? This
if ((I32)off =
Steve Peters wrote:
The attached patch converts t/op/vec.t to use test.pl for handling its
test cases rather than doing everything through Cprint statements.
Thanks, applied as #25202.
Robin Barker wrote:
I'm worried that allowing a Null pointer will still cause printf warnings.
Lack to tuits to look at this until next week.
But not allowing it will break API compatibility.
Robert Norris (via RT) wrote:
A Safe compartment with the default operators in place has read access
to any file that the calling process has permission to access.
--
#!/usr/bin/perl
use Safe;
my $c = Safe-new;
my $x = $c-reval(q(local (@ARGV, $/) = '/etc/passwd'; ));
print
On 7/12/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
Ok, enough dithering. Let's kill this bug.
File::Spec::Win32-canonpath() currently contains code to collapse .. so
whether or not it should continue to do so in the future is outside the
scope of this bug. That code is also
On 7/15/05, Michael G Schwern [EMAIL PROTECTED] wrote:
our $x; our $x; # no
Its not a mask but its useless and probably an oversight on the part of
the programmer. Maybe a Useless use of our? Or Repeated use of our?
I'm fine with dealing with that separately.
There's already the
On 7/13/05, Rick Delaney [EMAIL PROTECTED] wrote:
I agree too. The following patch will make the first case warn too.
Note that it also changes this current behaviour:
% perl -wle 'our $p; package X; our $p;'
% perl -wle 'our $p; package X; my $p;'
my variable $p masks earlier
Rick Delaney wrote:
On Tue, Jul 19, 2005 at 12:00:00PM +0200, Rafael Garcia-Suarez wrote:
On 7/15/05, Michael G Schwern [EMAIL PROTECTED] wrote:
our $x; our $x; # no
Its not a mask but its useless and probably an oversight on the part of
the programmer. Maybe a Useless use
Rafael Garcia-Suarez wrote:
There's already the warning our variable %s redeclared that can be
re-used for this.
Right. Do we want the
\t(Did you mean \local\ instead of \our\?)\n
part for this? It is unlikely that the programmer meant local in this
case.
Good
On 7/19/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Tue, Jul 19, 2005 at 11:31:01AM -0400, Scott R. Godin wrote:
I've had this itch to rip Pod::Html to shreds for a while now, and
refactor it to do the job more cleanly. Would anyone object to my taking
a whack at it?
It would
On 7/19/05, Adriano Ferreira [EMAIL PROTECTED] wrote:
On 7/19/05, Nicholas Clark [EMAIL PROTECTED] wrote:
But that doesn't rule out creating a minimal wrapper to provide Pod::Html's
interface.
But that would imply that wrapped modules should enter the Perl
distribution, because Pod::Html
SADAHIRO Tomoyuki wrote:
diff -ur perl~/pod/perlop.pod perl/pod/perlop.pod
--- perl~/pod/perlop.pod Fri Jul 15 18:33:32 2005
+++ perl/pod/perlop.pod Sun Jul 17 10:50:41 2005
@@ -1668,6 +1668,11 @@
the example above is not Cm//x, but rather Cm// with no C/x
modifier. So the
On 7/14/05, Rick Delaney [EMAIL PROTECTED] wrote:
Here's one way. Line 614 of t/op/re_tests fits the bill. I'm a little
disappointed that this patch didn't shake out any more bugs. I guess
we're getting close to a bug-free regex engine. ;-)
Thanks, almost a thousand tests added as change
Steve Hay wrote:
Removing those line breaks is definitely an improvement, but the patch
also inserts extra space into dl style lists - e.g. see the old and
new examples (from the Benchmark manpage) attached.
Looks fine to me, but before I commit it is anyone particularly wedded
to the
On 7/14/05, Robin Barker [EMAIL PROTECTED] wrote:
Attached patch reinstates VDf in blead perl to implement the %vd format,
which is still used in XS code and will reappear in blead for read-only
version numbers.
I have taken the opportunity to tidy up the code for the %p hacks that
are used
Andy Lester wrote:
Trying again
Thanks, applied (#25172).
Steve Hay wrote:
Thanks, applied as change #25171 to bleadperl.
This change causes tons of warnings like
not enough actual parameters for macro 'SVf_'
on Win32.
This is the bit of perl.h that causes them all:
#ifndef SVf_
# define SVf_(n) - #n p
#endif
#ifndef SVf
#
On 14 Jul 2005 04:20:24 -0700, Randal L. Schwartz merlyn@stonehenge.com wrote:
Michael Does anyone remember why it was decided our() should act this way?
Because our is like my. my $x ignores packages. Why shouldn't our
$x?
FWIW I'm with Randal there; our is about scoping, and its scope
On 7/15/05, Matt Sergeant [EMAIL PROTECTED] wrote:
In pod syntax, in order to have a contiguous verbatim section it all
needs to be indented by whitespace - even blank lines. This only tends
to show up in HTML pod viewers that add a different coloured background
to the verbatim sections. It's
On 7/15/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
So, to sum up... I think we all agree these should all warn.
my $x; our $x; # this currently does not
That's a bug.
our $x; my $x;
my $x; my $x;
our $x; our $x;
I disagree. This shouldn't warn. There is no
Rick Delaney wrote:
On Fri, Jul 15, 2005 at 05:01:46PM +0200, Rafael Garcia-Suarez wrote:
On 7/15/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
our $x; our $x;
I disagree. This shouldn't warn. There is no masking, as demonstrated by :
$ perl -e 'our $x=42; our $x; print $x
On 7/13/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
main::(-e:1): 0
DB1 @a = qw(A B C);
DB2 x $a[0..3], $a[1..3]
Surely you mean @a[0..3] here.
On 7/13/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] - Wed Dec 01 06:23:20 1999]:
Possible solutions:
Fix Cwd::abs_path(), so it doesn't do that. Possibly, rather
than warning and returning, it should use fast_abs_path() instead,
which should handle
On 7/12/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote:
You mention that you have wget. CPAN.pm triest wget last after trying
ncftp*. As its the most capable of all the options available it should
be tried first. Then lynx. Then finally ncftp*. A patch for this is
attached.
Can you
On 7/7/05, Michael G Schwern [EMAIL PROTECTED] wrote:
Its the most accurate with the least proliferation of platform-specific
hacks.
Is the core really the place for probing ?
I don't expect fs probing code to be sufficiently stable in the near
future to go in the core. Portability is always
On 7/7/05, Michael G Schwern [EMAIL PROTECTED] wrote:
The plan goes something like this:
* Offer to do a full probe at installation time (when we will likely be root).
Query the user about things like mount points. Cache the results.
In those days of package management software, most
On 7/5/05, Nick Ing-Simmons [EMAIL PROTECTED] wrote:
Probing for existing libz (shared or not) would help those of us
the embed perl in other things which already link zlib.
But IIUC zlib is embedded in a shared extension, not in perl itself.
On 7/6/05, Michael G Schwern [EMAIL PROTECTED] wrote:
I prefer no formatting because $foo is already visually distinctive enough.
We're used to seeing $foo from reading code.
Moreover pod2text adds quotes around code inside C, so $foo
sometimes breaks the clarity of the text.
On 5 Jul 2005 10:22:53 -, Steve Peters via RT
[EMAIL PROTECTED] wrote:
Cool! The new panic recently added caught this case.
[EMAIL PROTECTED]:~/perl-fix$ ./perl rt_3451.pl
panic: sv_upgrade to unknown type 255 at rt_3451.pl line 2.
That's not a fix. This bad upgrade really shouldn't
On 7/5/05, Brendan O'Dea [EMAIL PROTECTED] wrote:
Debian byg 227621 (http://bugs.debian.org/227621) reports OOM problems
processing /etc/group files with large lines.
I can't find this in the change log now, but I note in perl590delta :
For threaded Perls certain system database functions like
On 7/4/05, Steve Hay [EMAIL PROTECTED] wrote:
I currently have t/io/inplace.t and t/io/iprefix.t failing in bleadperl.
They fail complaining about tee and cat not being found on Win32.
Hardly surprising. But why is it even looking for them? It seems that
$^O has got corrupted, as per the
On 7/4/05, Michael G Schwern [EMAIL PROTECTED] wrote:
I'm going through some work to restore Test::More and Test::Harness to work
on 5.4.5, minor stuff really, and I'm wondering if its worth the trouble.
Has anyone seen 5.004_xx in the wild? And if so, were people actively
developing using
Starting tomorrow, I'm in vacation for two weeks.
I'll be reading my @gmail.com mail intermittently, (probably not the
other ones), and might be able to commit stuff, but I'd appreciate if
the current patches are applied by other commiters, since I don't want
to be overwhelmed by exploding
On 7/2/05, Dave Mitchell [EMAIL PROTECTED] wrote:
I've applied those of your Carp patches that don't effect dual-homed
modules (as determined by 'CPAN' = 1 in Porting/Maintainers.pl).
Since it isn't fixing critial bugs, I'm assuming its up to the authors
to decide.
Thanks, that's what I was
Dave Mitchell wrote:
Thinking further, rather than allowing lots of extra magics, just
unconditionally allow anything that is FAKE,READONLY.
Since a copy takes place, sounds OK to me.
--
Fix in six / Fix in six / You will need a new remix
Michael G Schwern wrote:
Exporter.t has warnings turned off presumably because of a peculiar way
in which a test has been written using barewords. If this was deliberate
I can't figure out why. It was introduced in 17988 by Nick.
http://public.activestate.com/cgi-bin/perlbrowse?patch=17988
Yitzchak Scott-Thoennes wrote:
Here's a first try at perlglossary.pod, mostly taken from the Camel
III Glossary courtesy of the nice folks at O'Reilly. Their lawyers
are still working out the exact licensing wording, but Tim gave the ok
to add this now.
buildtoc --build-all should be run.
Jarkko Hietaniemi wrote:
The information about the cross-compilation was a little bit dusty.
Thanks, applied as 25015.
Steve Peters wrote:
On Wed, Jun 29, 2005 at 11:56:10PM +0100, Dave Mitchell wrote:
On Wed, Jun 29, 2005 at 06:46:49PM -0400, Ronald J Kimball wrote:
not within any old conditional statement, only as the sole contents of a
*while* condition.
Or the conditional in a C-style for
Michael G Schwern wrote:
On Thu, Jun 30, 2005 at 09:57:22AM +0200, demerphq wrote:
On 6/30/05, Michael G Schwern [EMAIL PROTECTED] wrote:
Could have sworn I attached the tests.
Which time? :-)
Both times. Something's stripping them and it sure ain't on my end. Maybe
because I was
Tels wrote:
attached is the patch, and a testversion of t/uni/class.t (so that you can
toy around with it).
Thanks, applied.
I just changed this part :
+is ('first N-1 chars did not match', $blk);
(and the similar one below) to use the fail() function of test.pl instead.
The
David Dyck (via RT) wrote:
The following 3 line test program results in the same error when pushing
__PACKAGE__
onto @ISA:
our @ISA = qw(a b);
push @ISA, 'main';
push @ISA, __PACKAGE__;
Modification of a read-only value attempted at isabug.pl line 3.
Renaming the @ISA
David Dyck wrote:
On Thu, 30 Jun 2005 at 15:51 +0200, Rafael Garcia-Suarez wrote:
David Dyck (via RT) wrote:
The following 3 line test program results in the same error when pushing
__PACKAGE__
onto @ISA:
our @ISA = qw(a b);
push @ISA, 'main';
push @ISA, __PACKAGE__
Dave Mitchell wrote:
On Thu, Jun 30, 2005 at 11:43:33AM -0400, John Peacock wrote:
David Dyck wrote:
There's nothing to regenerate; the tokenizer has already eaten the
original contents and replaced it with PL_curstash:
...toke.c:4350 or so...
case KEY___PACKAGE__:
Michael G Schwern wrote:
-Moving::Target-import (foo);
+Moving::Target-import ('foo');
-::ok (foo eq foo, imported foo before EXPORT_OK changed);
+::ok (foo() eq This is foo, imported foo before EXPORT_OK changed);
I'm not sure you're not changing what is tested here.
[EMAIL PROTECTED] (via RT) wrote:
#!/usr/local/bin/perl
use warnings;
use strict;
my $n = 1;
my @data =
([ qw(a0 a1 a2 a3) ],
[ qw(b0 b1 b2 b3) ],
[ qw(c0 c1 c2 c3) ],
);
use Data::Dumper;
There are no array slices in your examples. In a [] subscript,
Avis, Ed wrote:
There are no array slices in your examples. In a [] subscript,
expressions are evaluated in scalar context.
Well, not in the case of
@a[0, 1, 2]
It is tempting for the programmer to try the same thing with a listref:
$r-[0, 1, 2]
although in fact the
Tels wrote:
A: If the tests are not equivalent, what did I do wrong?
The tests are not strictly equivalent. In your version :
+ my $qr = qr/(\p{$blk}+)/; $str =~ /$qr/;
+ is ($1, substr($str, 0, -1)); # all except last char
you don't guarantee that $1 comes from the previous
Jarkko Hietaniemi wrote:
...
cd t
LD_LIBRARY_PATH=/cluster/members/member0/tmp/jhi/perl-5.9.x:/tmp/jhi/perl-5.9.x
./perl TEST -deparse /dev/tty
--
TESTING DEPARSER
Rafael Garcia-Suarez wrote:
maint isn't happy with this file as well.
I committed a general fix :
It doesn't seem to break deparsing of more regular variables.
Change 25005 by [EMAIL PROTECTED] on 2005/06/28 11:17:30
B::Deparse was chocking on variable names with colons (like foo
I notice that the testsuite of Crypt::DSA 0.13 hangs when built with 5.8.7,
and passes when built with 5.8.6.
I read in the changelog :
0.13 2005.05.26
- Rewrote to use Math::BigInt instead of Math::Pari, including patches
from Brad Fitzpatrick for a replacement for the isprime
Tels wrote:
Tels, can you reproduce this problem ?
Not yet (5.8.6, BigInt 1.77, FastCalc 0.10).
Maybe the test just gets much slower because it took quite a while at test
3 in 06_fibs.t for me.
A while ? might be. I thought it hanged. (the build machine was quite loaded)
OK, so that's
On 28 Jun 2005 12:36:09 -, via RT Ronan Le Hy
[EMAIL PROTECTED] wrote:
% perl -e 'map $1 ()'
panic: ck_grep at -e line 1.
Happens with 5.8.7 (as below), and 5.9.3, as downloaded on 28/06/2005 from
rsync://ftp.linux.activestate.com/perl-current/
Actually, that's a feature :
Change
101 - 200 of 949 matches
Mail list logo
