that's just weird. I think at this point you're going to have to go
in and poke around with the debugger.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
it using fresh_perl_like().
fresh_perl_like('CODE', qr/bar/);
my $w = sub { warn q(bar) }; local $SIG{__WARN__} = sub { goto $w; }; warn
q(foo);
CODE
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Insulting our readers is part of our business model.
http
[EMAIL PROTECTED] - Sat Aug 30 14:33:01 2003]:
perl -wle '(1x5683)=~ /^(11+)\1+$/'
works ok
perl -wle '(1x 9973)=~ /^(11+)\1+$/'
Segmentation fault (core dumped)
ulimit -a
core file size (blocks) unlimited
data seg size (kbytes) unlimited
file size (blocks)
[EMAIL PROTECTED] - Sat Jun 19 11:06:22 2004]:
perl -wle 'sub foo { return 1..5} print sort foo(8)'
8
while a bit annoying (I wanted to sort the result of foo applied to
8),
this is actually what is documented as the
sort SUBNAME LIST
form of sort. foo is the subname and there is
[rhesa - Wed Apr 28 11:12:56 2004]:
Class::Struct allows you to override the accessors it creates, but it
doesn't call them in its constructor.
In other words,
$struct-field('blah');
calls my override, but
$struct = structure-new('field' = 'blah');
doesn't.
of Terror.
If only there was a POD KOMMISSAR here to help us decide!
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything.'
-- Witches Abroad by Terry Prachett
is of course taken care of
by the assignment operator.
Sounds ok to me.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Insulting our readers is part of our business model.
http://somethingpositive.net/sp07122005.shtml
On Wed, Jul 13, 2005 at 04:43:15PM -0700, Michael G Schwern wrote:
$ bleadperl -wle 'package Foo; Foo-VERSION'
Bus error
Segfaults are handled with fresh_perl_is/like(). Unfortunately
t/op/universal.t uses ad hoc testing so I'll have to convert it to t/test.pl
first.
Back in a bit.
Ok
may fetch it yourself from your nearest archive site.)
Does that bear any relation to reality?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything
[RT_System - Mon Mar 04 21:30:58 2002]:
This is an alternative and it confirmes the bug in 5.6.1:
% /usr/local/perl-5.6.1/bin/perl -le '
$_ = \xF9 \xF6;
print /\xF9\s+?\xF6/ ? ok : not ok;
'
not ok
The bug is fixed in perl-5.7.3 and the fix will be in 5.8.0 and 5.6.2.
Confirmed
12, 2005.
I'm not sure whether to shed a tear or throw a party.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
ROCKS FALL! EVERYONE DIES!
http://www.somethingpositive.net/sp05032002.shtml
On Fri, Jul 15, 2005 at 10:14:04AM +0200, H.Merijn Brand wrote:
Does that answer the question?
Yep. Now do we put all that into the Configure header?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
ROCKS FALL! EVERYONE DIES!
http
On Fri, Jul 15, 2005 at 10:15:46AM +0200, H.Merijn Brand wrote:
I'm not sure whether to shed a tear or throw a party.
How about a patch to README.os2 ?
To say what? Our condolences that your operating system was discontinued?
--
Michael G Schwern [EMAIL PROTECTED] http
right.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked and wrong to have broken inside and peeked at the
implementation and then relied upon it.
-- tchrist in [EMAIL PROTECTED]
[EMAIL PROTECTED] - Tue Jul 12 03:24:42 2005]:
It would be nice if CPAN.pm supported curl as a download method.
Particularly because OS X ships with *none* of the currently handled
methods (wget, lynx, ncftp*).
Well that was surprisingly easy. Patch attached.
It makes curl the first
schwern Exp schwern $
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Just call me 'Moron Sugar'.
http://www.somethingpositive.net/sp05182002.shtml
[abigail - Sat Sep 02 03:39:24 2000]:
$ perl -we '$@ = [foo\n]; print [EMAIL PROTECTED]@[EMAIL PROTECTED]'
foo
$ perl -MO=Deparse -we '$@ = [foo\n]; print [EMAIL PROTECTED]@[EMAIL
PROTECTED]'
$@ = [foo\n];
print ${$@;[EMAIL PROTECTED]@;}];
-e syntax OK
$
[EMAIL PROTECTED] - Tue Jan 20 02:14:31 2004]:
I've attached the fix, and included the segfault protection afforded
by the previous patch (it now uses the nearby CROAK code path). I'm
sure that the problem will apply to at least one other piece of the
code so when I stumble across it I'll
is
unimplemented);
Minor nit. Those are better written with like():
like( $@, qr/^The fchdir function is unimplementated at/,
fchdir is unimplemented );
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked and wrong to have broken
On Fri, Jul 15, 2005 at 10:33:36AM +0100, Steve Hay wrote:
Thanks. Applied as change 25149 with
%hash = ( key = $value );
changed to
%hash = ( $key = $value );
(which I think is what you intended given the context.)
Good point.
--
Michael G Schwern [EMAIL PROTECTED] http
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.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a dish
;
package Bar;
our $bar = 30; # declares $Bar::bar for rest of lexical scope
print $bar; # prints 30
our $bar; # emits warning but has no other effect
print $bar; # still prints 30
--
Michael G Schwern [EMAIL PROTECTED] http
[EMAIL PROTECTED] - Thu May 31 05:01:54 2001]:
#!/usr/bin/perl
my $addr = 192.168.2.2; # or any non-reachable address
my $port = 5010;
use IO::Socket;
my $sock = IO::Socket::INET-new(PeerAddr=$addr,
PeerPort=$port,
[w.briscoe - Mon Jul 15 17:29:27 2002]:
I got the following diagnostic:
cl -c [...] SDBM_File.c
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for
80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
SDBM_File.c
SDBM_File.c(296) : warning C4700: local
approach things would be a lot more sustainable.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Just call me 'Moron Sugar'.
http://www.somethingpositive.net/sp05182002.shtml
When run using 5.8.6 and ithreads perl thinks for a while and then sez:
$ perl ~/tmp/test
A thread exited while 4 threads were running.
So this looks like an issue in Thread::Queue and not 5.005threads.
Unless the sample code is not sane, but I don't know threads well enough
to evaluate that.
[EMAIL PROTECTED] - Sun Jun 23 02:21:24 2002]:
Having tried to share objects by writing stuff along the lines:
my $a : shared = new FOOBAR;
It took a posting to comp.lang.perl.misc before I realised the error
of my ways:
my $a = new FOOBAR;
share($a);
I don't think the
[EMAIL PROTECTED] - Wed Nov 20 08:26:56 2002]:
I am following the steps in the README.os390 file and I have applied
the
fix to makedepend.SH (provided by Peter Prymmer) with regard to the
unwanted removal of the last #endif statement in perly.c as below:
--- makedepend.SH.orig Mon
[radknee - Sun Dec 08 09:15:16 2002]:
Using CPAN I did 'install DBD::PG'. Config went ok, but make produced the
errors below. When I recompiled perl without threads make went ok.
[systame1:local/src/DBD-Pg-1.13] randy% make
cc -c -I/usr/local/pgsql/include
[davem - Tue Sep 23 17:09:43 2003]:
On Mon, Sep 22, 2003 at 05:01:19PM -, David Buckley wrote:
use threads;
use threads::shared;
use Data::Dumper;
our $a : shared;
$a = \$a;
print Data::Dumper::Dumper( $a );
This produces a short pause, then a segfault.
The segfault is
[EMAIL PROTECTED] - Tue Nov 04 00:39:47 2003]:
Perl crashes on the following test program:
use threads;
use threads::shared;
my %hash : shared;
exists $hash{1};
The error message is: 'Free to wrong pool 15d26e8 not 1aeb8f0.'
From reading the discussion of this ticket it seems that
On Wed, Jul 13, 2005 at 07:43:13PM -0400, Joshua Kronengold wrote:
On Wed, 13 Jul 2005 7:17 pm, Michael G Schwern via RT wrote:
The bleadperl version tries both getcwd() and cwd(). Both fail.
In fact, nothing works:
I think shelling out usually works (on unixlike systems) as a last
resort
[dmlloyd - Tue Aug 14 04:33:09 2001]:
If you extract the attached module and do this:
perl Makefile.PL
make
perl -Mblib -MBugDemo -e 'BugDemo-querble = 1234'
in perl 5.6.1, it works but in 5.7.2, you get:
Can't modify non-lvalue subroutine call at -e line 1.
[EMAIL PROTECTED] - Mon Feb 23 15:11:06 2004]:
Test case #0:
perl -e '$eol = qr/$/m; foo\nbar\n =~ /$eol/; print $-[0], \n'
Test case #1:
perl -e '$eol = qr/$/m; foo\nbar\n =~ /$eol(?:)/; print $-[0],
\n'
I'm getting the answer 7 from case #0 and 3 from case #1. The
--
bridge.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know what's normal.
-- Lords and Ladies by Terry Prachett
On Thu, Jul 14, 2005 at 07:11:41AM -0400, Joshua Kronengold wrote:
On Thu, 14 Jul 2005 6:37 am, Michael G Schwern wrote:
One of the things Cwd tries is `pwd`. It doesn't work because it
doesn't
have any more information to go on than Perl does.
Wow.
Um -- what are the perms
On Thu, Jul 14, 2005 at 10:10:59AM -0400, Rick Delaney wrote:
to t/op/re_tests would suffice. But that doesn't test the embedding of
a qr/pattern/m in another pattern.
Sounds like a fine hammer to hit the regex engine with.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com
will
do a better job.
Know any?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
ROCKS FALL! EVERYONE DIES!
http://www.somethingpositive.net/sp05032002.shtml
So, to sum up... I think we all agree these should all warn.
my $x; our $x; # this currently does not
our $x; my $x;
my $x; my $x;
our $x; our $x;
and that this should not
package Foo;
our $x;
package Bar;
our $x;
but this appears to be up in the air:
[EMAIL PROTECTED] - Tue Oct 23 22:13:02 2001]:
#! /usr/bin/perl -w
use strict;
use 5.6.0;
use constant HASH_KEY1 = 100;
use constant HASH_KEY2 = 200;
our %hash_desc = (
HASH_KEY1 = This is hash key one,
HASH_KEY2 = This is hash key two
);
foreach my $h_desc (
[schwern - Thu Jul 14 16:47:07 2005]:
= is documented as follows:
The = digraph is mostly just a synonym for the comma operator. It's
useful for documenting arguments that come in pairs. As of release
5.001, it also forces any word to the left of it to be interpreted as a
string.
to the argument that:
package Foo;
our $x = 42;
package Bar;
my $x = 23;
has been warning since 5.6.x and I can't recall anyone complaining.
Switching my and our around doesn't really change the scenario.
--
Michael G Schwern [EMAIL PROTECTED] http
[ysth - Wed Jul 13 14:13:53 2005]:
Wording looks good, but I'd prefer to see Cuse strict 'vars'.
Here it is again with that fixed plus the simple explaination lifted
from Randal's column.
http://www.stonehenge.com/merlyn/UnixReview/col54.html
I also clarified in the cross-package example
[EMAIL PROTECTED] - Sat May 05 21:48:58 2001]:
. I run my perl scripts through cpp (for various reasons). I can't
use
the -P option because I use libraries and such which all need to be
run
through cpp.
. The output from cpp contains # lines of the form (for example):
# 1
Anybody tried djgpp in a while?
=0xec09c) at
/SourceCache/Csu/Csu-47/crt.c:267
#513 0x8fe1a278 in __dyld__dyld_start ()
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a dish that is best
served cold? And it is very cold on the Internet!
goto $warn; # this segfaults
};
warn foo;
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know what's normal.
-- Lords and Ladies by Terry Prachett
That's clearly masking. our is lexical even crossing package boundries
(something I never realized). Declaring the same lexical variable in the
same lexical scope, whether by my or our, is masking.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked
been gutted to use ithreads.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a dish that is best
served cold? And it is very cold on the Internet!
control for.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know what's normal.
-- Lords and Ladies by Terry Prachett
.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
, perl$], perl5,
perl. But that's another bug.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know what's normal.
-- Lords and Ladies by Terry Prachett
. That behavior seems like a misfeature and just asking
for a gotcha in multi-package files. I'd argue it should be deprecated.
Does anyone remember why it was decided our() should act this way?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked and wrong
'}.::}-{$kid} }
+defined { ${$self-{'curstash'}.::}{$kid} }
!exists
$self-{'subs_deparsed'}{$self-{'curstash'}.::.$kid}
defined prototype $self-{'curstash'}.::.$kid
--
Michael G Schwern [EMAIL PROTECTED] http
On Wed, Jul 13, 2005 at 10:12:25AM +0200, Rafael Garcia-Suarez wrote:
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.
Just replicating what the bug claimed.
main::(-e:1
. This
is assumed from the header Display Information.
Better to drop the mnemonic than use a misleading or vague one.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a dish that is best
served cold? And it is very cold
to have been kept up to date.
CORE::chdir would have to do that and it doesn't. Sure would be nice if
it did though.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
= qw(Foo);
package Bar;
@ISA = qw(Baz);
print @ISA; # Hmm, everything looks ok.
print @Foo::ISA;# SURPRISE!
print @Bar::ISA;
No warnings issued and strict won't save you.
--
Michael G Schwern [EMAIL PROTECTED] http
for the username)?
I can see that for the username but not for the password.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything.'
-- Witches Abroad by Terry
) could be tried on the newer FreeBSD to see if its Perl or FreeBSD
which was fixed. But not necessary.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Reality is that which, when you stop believing in it, doesn't go away.
-- Phillip K. Dick
$ bleadperl -wle 'package Foo; Foo-VERSION'
Bus error
Segfaults are handled with fresh_perl_is/like(). Unfortunately
t/op/universal.t uses ad hoc testing so I'll have to convert it to t/test.pl
first.
Back in a bit.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
On Wed, Jul 13, 2005 at 03:31:58PM +0100, [EMAIL PROTECTED] wrote:
Michael G Schwern via RT [EMAIL PROTECTED] wrote:
:5.005 threads are due to be eliminated in 5.10. Closing this bug.
This seems like an inappropriate justification for closing the bug:
if there is a bug in (eg) 5.8.x
[nicholas - Wed Jul 13 08:59:06 2005]:
So I'm in the nominations for the Schwern award for the committer who
leaves
the most tickets open ? Not the most prestigious of titles to gain.
The deciding factor for the judges was leaving this very ticket open.
Masterful! ;P
You'll be receiving
;
my $Foo::foo = 42;
package Bar;
print $foo; # doesn't work because this is $Bar::foo
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know what's normal.
-- Lords and Ladies by Terry Prachett
On Wed, Jul 13, 2005 at 08:33:12PM -0400, [EMAIL PROTECTED] wrote:
On Wed, Jul 13, 2005 at 04:29:53PM -0700, Michael G Schwern wrote:
I don't see the utility of the current behavior, except maybe it was easier
to implement, and IMHO its ripe for mistakes like the one pointed out
earlier
[EMAIL PROTECTED] - Tue Sep 07 06:28:44 2004]:
I disagree with the final thought there. My machine did have a copy
of wget on it so that wasn't the problem in my case (though it would be
for a stock install of the current version of Mac OS X). Since it does
present a problem for certain
The attached patch changes all the unsafe uses of rename() to
File::Copy::move(). These are the ones which move a path to a different
directory. All the rest work within the same dir and should be safe.
CPAN.pm.patch
Description: Binary data
On Mon, Jul 11, 2005 at 11:19:06PM -0700, Michael G Schwern via RT wrote:
CPAN.pm could check if the proto is HTTP and not try ncftp* but as they
will be the last thing tried I think its more useful to try them than
not. Who knows, maybe ncftpget will handle http urls in the future?
Also
[EMAIL PROTECTED] - Thu Oct 23 06:01:05 2003]:
The online help of the CPAN shell has this entry:
rNONE reinstall recommendations
I checked with multiple coworkers and all of them (including
me) misunderstood this as a command installing something.
It should be made
[EMAIL PROTECTED] - Thu Dec 18 15:43:42 2003]:
When I started cpan for the first time on perl-5.8.2 and started the
configuration process I was cutting and pasting from a file. I grabbed
the
cpan directory location with leading spaces and pasted it.
The results were this as the next
Forgot to CC p5p with my patch. Pumpkings and pumpkinglets, there's a
patch for this bug. Please have a look at it in RT.
my sock
drawer. On Pluto.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Just call me 'Moron Sugar'.
http://www.somethingpositive.net/sp05182002.shtml
On Tue, Jul 12, 2005 at 05:09:15AM -0500, Steve Peters wrote:
On Tue, Jul 12, 2005 at 12:00:02PM +0200, Rafael Garcia-Suarez wrote:
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
$sock-atmark;
+$sock-read($data, 1024) until $sock-atmark;
Note: this is a reasonably new addition to the family of socket
functions, so all systems may not support this yet. If it is
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
You are wicked and wrong
release. As for stable
you'll just have to watch the Changes log of the next 5.8.x release.
And hopefully this will make it into the CPAN version of CPAN.pm.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Ahh email, my old friend. Do you know that revenge is a dish
. Because it chdir'd to the build directory before trying to resolve
my relative $^X it could not find it. So in desperation it started looking
through my PATH and found /sw/bin/perl.
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
Don't try the paranormal until you know
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 busted and is the source of this bug.
Attached is a patch to fix this
Some documentation of the meta characters has been added to File::Glob
but not much else. Just how much documentation of globbing do we want
to put in the docs and how much can be go read X? Maybe a reference
to a Unix tutorial on how globbing works?
The attached patch changes copy() so that it carps instead of croaking
when its asked to copy identical files. This is better because asking
to copy identical files is not an error (and the operation suceeds) its
just dubious.
I also added a check in move() to ensure it gets the right number of
This bug appears to have been resolved somewhere before 5.8.6. The
construct no longer consumes additional memory.
This problem still exists in 5.8.6 and [EMAIL PROTECTED]
[EMAIL PROTECTED] - Sun Feb 13 23:29:43 2000]:
When going out of range at the prompt in the debugger - i.e.
pressing
ctrl-n when there is no next line, or backspace when I'm at the start
of the
line, it crashes.
I am unable to reproduce this but using 5.5.4 and Term::ReadLine::Gnu
1.08.
The debugger no longer sets $.
$ perl -de 0
Loading DB routines from perl5db.pl version 1.28
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
main::(-e:1): 0
DB1 print $.
DB2
The code works the same in the debugger as it does on the command line:
[EMAIL PROTECTED] - Thu Apr 05 19:58:47 2001]:
The Perl debugger outputs strings containing the character
ctrl-\ wrongly when using the x command. For example,
x chr(28) results in \c\ and x \c\\ results in \c\\\.
The results, however, are not valid Perl and will result in
string terminator
On Tue, Jul 12, 2005 at 06:19:48PM -0400, Randy W. Sims wrote:
Michael G Schwern via RT wrote:
The attached patch changes copy() so that it carps instead of croaking
when its asked to copy identical files. This is better because asking
to copy identical files is not an error
This appears to have been fixed in the latest development version of perl.
Still an issue in 5.8.6 and [EMAIL PROTECTED]
This appears to have been fixed in the 5.8 track. With 5.8.6 I can
ctrl-c at the accept() call and I am dumped into the debugger at the
proper place. With 5.5.4 it didn't respond to ctrl-c at all, I wasn't
dumped into the debugger nor did the process exit. So I'm reasonably
sure this is
[joemcmahon - Fri Jun 03 15:00:45 2005]:
Same program in the debugger:
% perl -de '
$_ = \x{100};
s/[\x{100}]/o/;
print $_\n;
'
Loading DB routines from perl5db.pl version 1.19
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
[EMAIL PROTECTED] - Sun Jun 22 23:53:28 2003]:
-
The debugger command x works as expected, but |x shows no output
at all:
I am unable to reproduce this problem. What pager does the debugger
think you're using? You can find
Joe's patch appears to have gone in.
$ bleadperl -de 1
Loading DB routines from perl5db.pl version 1.28
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
main::(-e:1): 1
DB1 x bless {}, Foo
0 Foo=HASH(0x810850)
empty hash
DB2 x bless \{}, Foo
0
[nicholas - Tue Jun 07 14:40:34 2005]:
Thanks for the report. Rafael also spotted this about 8 hours ago. It's
my fault (change 24714) and should be fixed by 24732.
Was it?
[EMAIL PROTECTED] - Wed Jun 29 15:20:13 2005]:
- the script starts here --
use Encode qw/encode decode/;
my $var = +AQUBBQEF-/b+AXwBfAF8-;
my $decoded = decode (UTF-7, $var);
my $encoded = encode (UTF-7, $decoded);
print $encoded;
- the script ends here -
when
and deleting code, that
this is true and we're go for removing all the 5005threads code in 5.10?
--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern
'All anyone gets in a mirror is themselves,' she said. 'But what you
gets in a good gumbo is everything
[RT_System - Sun Sep 19 18:30:17 1999]:
I appear to be running into a memory leak in IO::Socket which I can't
fix. The
following example:
#!/usr/bin/perl -w
use strict;
use IO::Socket;
my $RemoteHost = 'localhost';
while (1) {
my $Socket = new IO::Socket::INET(PeerAddr =
[RT_System - Sun Sep 19 20:00:34 1999]:
This is with _61 ( perl -wc doesn't report any errors )
use strict;
for my $i (1..5) {
if ( $i == 2 ) { next Loop; }
}
I presume you're reporting that perl -cw does not report the lack of a
loop label as an error? This is correct because a
[RT_System - Mon Sep 20 02:46:44 1999]:
Ah, I think I see what you mean now. You want these to behave
differently:
DB1 print $count = @array = ((undef) x 3)[0,1,2]
0
DB2 print $count = @array = ()[0,1,2]
0
You'd have the first version start returning three, but leave
[RT_System - Mon Sep 20 05:51:22 1999]:
For some obscure reasons I did test the %! auto-require stuff yesterday
and found that it doesn't work (in Perl 5.005_03 and 5.005_61). Well
actually it does work at runtime, just not at compile-time, exactly as the
comments indicate. But isn't this
101 - 200 of 839 matches
Mail list logo
