Re: Why does our() cross packages? (PATCH)

Muy fantastico! Do declarations assign variables to names or do we assign names to variables? Although it sounds horrendous, i think that "we assign a fresh variable to the name" is more correct. Assigning something to a variable is of course taken care of by the assignment operator. ... U

Smoke [5.9.3] 25156 FAIL(M) MSWin32 WinXP/.Net SP1 (x86/1 cpu)

Automated smoke report for 5.9.3 patch 25156 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 2 hours 30 minutes (average 4 minutes 42.094 seconds) Summary: FAIL(M) O = OK F =

[perl #10076] RC3 ineffective ext/SDBM_File/SDBM_File.c compiler silencing

> [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 C4

[perl #7067] Errno error in IO::Socket::INET

> [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, >

Re: [perl #21461] perl5.6.1 dos (djgpp) source build broke

i still use their bash and window, on a win95 machine but abandoned their perl in favor of ActiveState. Not only did it not build right, but MakeMaker et al were very problematic. recently i installed rxvt under cygwin for a xp machine which seems like the way to go. "H. Merijn Brand via RT"

Re: Why does our() cross packages? (PATCH)

On Fri, Jul 15, 2005 at 03:59:13PM -0500, David Nicol wrote: > How does the attached patch grab you? Piecing it together, these are the leading paragraphs: Unlike C, which both allocates storage for a variable and assigns a simple name to that storage for use within the current scope, C

Re: Why does our() cross packages? (PATCH)

How does the attached patch grab you? -- David L Nicol Aesop's fables, with text-sensitive advertising: http://cronos.advenge.com/pc/aesop/start.html --- perlfunc.pod.old 2005-07-15 15:08:38.12500 -0500 +++ perlfunc.pod 2005-07-15 15:49:50.765625000 -0500 @@ -3198,19 +3198,21 @@ =item our

Re: [perl #2915] Inconsistent warnings with "our"

On Fri, Jul 15, 2005 at 11:46:42AM -0400, Rick Delaney wrote: > Here's a new summary of masking warnings: > > # Warns > my $x; my $x; # yes > my $x; our $x; # yes > our $x; my $x; # yes > our $x; our $x; # no Its not a mask but its us

Re: [PATCH] more embed cleanup

Andy Lester wrote: >I'm down to about 380 function parms to verify. > Thanks. Applied as change 25156. Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the ad

Re: [perl #36514] Add curl support to CPAN.pm

Michael G Schwern via RT wrote: >>[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

Re: [PATCH blead] Re: [perl #3269] no warnings "foo" without "use warnings" turns off all warnings.

Rick Delaney wrote: >>I wonder what other accidentally supressed warnings this is going to >>dig up. >> >> > >Not too many from `make test`. Just these: > >t/op/inc.. >Parentheses missing around "my" list at op/inc.t line 163. >Parentheses missing a

Re: [PATCH] RE: blead: no longer supports %vd format

Robin Barker 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. Can someone apply this pretty please? Robin mispoke a little, in that "%vd" will be used in the core again once

Re: [PATCH blead] Re: [perl #3269] no warnings "foo" without "use warnings" turns off all warnings.

Michael G Schwern wrote: >On Wed, Jul 13, 2005 at 03:48:26AM -0400, Rick Delaney wrote: > > >>This patch breaks test 37 of ext/B/t/deparse.t because this warning: >> >> # [Using a hash as a reference is deprecated at lib/B/Deparse.pm line 3151. >> >>is no longer suppressed by C. >> >> > >I t

Re: [perl #2915] Inconsistent warnings with "our"

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

Re: [perl #3177] perl -d treats $array[0..3] differently than non-debugger

On Jul 13, Michael G Schwern said: 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 DB<1> @a = qw(A B C); DB<2> x $a[0..3], $a[1..3] Surely you mean @a[0..3] here. Just replicating w

[PATCH] more embed cleanup

I'm down to about 380 function parms to verify. dump.c: Consting. embed.fnc: Many more NN and NULLOKs added. Added uiv_2buf, need_utf8 and first_symbol. hv.c: Consting. Removed a redundant statement that set a loop variable to the value it was already set to. op.c: Consting. perl.c: Consting

Re: [perl #2915] Inconsistent warnings with "our"

Here's a new summary of masking warnings: # Warns my $x; my $x; # yes my $x; our $x; # yes our $x; my $x; # yes our $x; our $x; # no # Warns my $x; package X; my $x; # yes my $x; package X; o

Re: fchmod, fchown, fchdir

"H.Merijn Brand" <[EMAIL PROTECTED]> writes: > On Fri, 15 Jul 2005 02:57:05 -0700, Michael G Schwern <[EMAIL PROTECTED]> > wrote: > > > On Fri, Jul 15, 2005 at 02:32:50AM -0700, Gisle Aas wrote: > > +ok($@ =~ /^The fchmod function is unimplemented at/, "fchmod is > > unimplemented"); > > > +

Re: [perl #2915] Inconsistent warnings with "our"

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' > 42 Hmm, I'm in

Re: fchmod, fchown, fchdir

On Fri, 15 Jul 2005 02:57:05 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Fri, Jul 15, 2005 at 02:32:50AM -0700, Gisle Aas wrote: > +ok($@ =~ /^The fchmod function is unimplemented at/, "fchmod is > unimplemented"); > > +ok($@ =~ /^The fchown function is unimplemented at/, "fc

Re: [perl #2915] Inconsistent warnings with "our"

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

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

On 15 Jul 2005, at 08:03, H.Merijn Brand wrote: If you think this is worthwhile, please send a new attached patch. Note however the subsequent patches might act more or less like what I experienced and the trailing spaces get lost again. Your call Nah, I was just letting you know why I did it

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

Nicholas Clark wrote: Content-Type: text/plain; charset=US-ASCII; format=flowed format=flawed, as John Peacock put it politely. I wish I *had* been the one to think of that originally Attachments are required for many/most e-mail clients if you want to correctly preserve whitespace change

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

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.

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

On Fri, 15 Jul 2005 07:36:59 -0400, Matt Sergeant <[EMAIL PROTECTED]> wrote: > On 15 Jul 2005, at 03:20, H.Merijn Brand wrote: > > > On Thu, 14 Jul 2005 16:53:03 -0400, Matt Sergeant <[EMAIL PROTECTED]> > > wrote: > > > >> Simple patch for an obvious omission (also fixes the lack of > >> whites

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

On Fri, Jul 15, 2005 at 07:36:59AM -0400, Matt Sergeant wrote: > How nice of my mailer to strip trailing whitespace for me :-) Content-Type: text/plain; charset=US-ASCII; format=flowed format=flawed, as John Peacock put it politely. IIRC Jarkko experimented and he found it impossible to disab

Smoke [5.9.3] 25145 FAIL(F) bsd/os 4.1 (i386/1 cpu)

Automated smoke report for 5.9.3 patch 25145 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 54 minutes (average 1 hour 57 minutes) Summary: FAIL(F) O = OK F = Failure(s), extended repor

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

On 15 Jul 2005, at 03:20, H.Merijn Brand wrote: On Thu, 14 Jul 2005 16:53:03 -0400, Matt Sergeant <[EMAIL PROTECTED]> wrote: Simple patch for an obvious omission (also fixes the lack of whitespace on the line before untie()): In this patch I see no whitespace changes at all, nor do I see t

Re: PERL_DONT_CREATE_GVSV needs to be #define'd somewhere else

Nicholas Clark wrote: >On Thu, Jul 14, 2005 at 04:25:41PM +0100, Steve Hay wrote: > > > >>I may also do the other thing that I suggested *as well* - namely, >>cutting down the canned config.h's to a minimal configuration so that >>plan B is easier to fall back on if this doesn't work out. >> >

Re: metaconfig instructions in Configure out of date?

On Fri, 15 Jul 2005 02:17:15 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Fri, Jul 15, 2005 at 10:51:18AM +0200, H.Merijn Brand wrote: > > > Yep. Now do we put all that into the Configure header? > > > > No. > > > > 1. People are scared off enough already by the sheer size of it > >

Re: [perl #7840] Hash Behaviour differs v5.6.0 to v5.6.1

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]

Re: fchmod, fchown, fchdir

On Fri, Jul 15, 2005 at 02:32:50AM -0700, Gisle Aas wrote: +ok($@ =~ /^The fchmod function is unimplemented at/, "fchmod is unimplemented"); > +ok($@ =~ /^The fchown function is unimplemented at/, "fchown is > unimplemented"); > +ok($@ =~ /^The fchdir function is unimplemented at/, "

Re: PERL_DONT_CREATE_GVSV needs to be #define'd somewhere else

On Thu, Jul 14, 2005 at 04:25:41PM +0100, Steve Hay wrote: > I may also do the other thing that I suggested *as well* - namely, > cutting down the canned config.h's to a minimal configuration so that > plan B is easier to fall back on if this doesn't work out. > > Shall I commit it? I don't kn

Re: [perl #7840] Hash Behaviour differs v5.6.0 to v5.6.1

Michael G Schwern via RT wrote: >>[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

Re: fchmod, fchown, fchdir

"H.Merijn Brand" <[EMAIL PROTECTED]> writes: > I'll just wait for the full patch, which I presume also has several test > cases along with it. Here you go... diff -ru perl-current/doio.c perl-hack/doio.c --- perl-current/doio.c 2005-07-13 02:49:00.0 +0200 +++ perl-hack/doio.c2005-07-

[perl #25145] Storable segfaults with B::Deparse + overload + cyclic structures

> [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

[perl #4207] Deparse generating unparsable code.

> [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

AW: [perl #8840] perl 5.6.2 source distributen for wins2

5.6.2 seems to be better 5.8.7 has a problem with the debugger. I spend a Day to install it reinstall package but I forgot to notoce the excatly message something. The problem is Readterm cannot detremine window size something like this. Michael -Ursprüngliche Nachricht- Von: Michae

Re: [PATCH] Configure grammar nit

On Fri, Jul 15, 2005 at 10:54:18AM +0200, H.Merijn Brand wrote: > I'll do that, but I will not generate a new Configure until a *real* change > makes it necessary (did I spell that right?) Yes, but "right" is an adjective, so you shouldn't be using it with a verb ("spell"). Hence "did I spell that

Re: metaconfig instructions in Configure out of date?

On Fri, Jul 15, 2005 at 10:51:18AM +0200, H.Merijn Brand wrote: > > Yep. Now do we put all that into the Configure header? > > No. > > 1. People are scared off enough already by the sheer size of it > 2. There is already enough writing for it in Porting/ Should we strip out what's there and poi

[perl #36514] Add curl support to CPAN.pm

> [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 c

Re: Typo in t/op/stat.t

Found yet another strangeness in that file. chown() is called with the filename as the second argument, but the second argument is supposed to be the gid. It means that the chown() call in stat.t has always been a noop. This patch make the chown functional, but I still don't think it does anythin

Re: Why does our() cross packages?

On 14 Jul 2005 04:20:24 -0700, Randal L. Schwartz 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 works ex

Re: [PATCH] Configure grammar nit

On Fri, 15 Jul 2005 01:22:06 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > rt.perl.org 7327 mentioned a little grammar nit in Configure. > > --- Configure 2005/07/15 08:19:07 1.1 > +++ Configure 2005/07/15 08:19:19 > @@ -7758,7 +7758,7 @@ > your system supports dynamic loading

Re: metaconfig instructions in Configure out of date?

On Fri, 15 Jul 2005 01:18:27 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > 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? No. 1. People are scared off enough already by the sh

[PATCH] Configure grammar nit

rt.perl.org 7327 mentioned a little grammar nit in Configure. --- Configure 2005/07/15 08:19:07 1.1 +++ Configure 2005/07/15 08:19:19 @@ -7758,7 +7758,7 @@ your system supports dynamic loading, it is probably possible to build a shared libperl.$so. If you will have more than one exe

Re: RIP OS/2

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://www

Re: metaconfig instructions in Configure out of date?

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://www.somethingpositive.n

Re: [perl #36538] perlfunc/our contradicts itself

Michael G Schwern via RT wrote: >>[ysth - Wed Jul 13 14:13:53 2005]: >> >>Wording looks good, but I'd prefer to see C. >> >> > >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 clarifie

Re: RIP OS/2

On Fri, 15 Jul 2005 01:07:53 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > http://theinquirer.net/?article=24625 > > BIG BLUE has hammered the final nails into OS/2's coffin. It said that > all sales of OS/2 will end on the 23rd of December this year, and support > for the pre-emp

Re: [perl #24691] leading spaces on cpan configuration causes failure

Michael G Schwern wrote: >On Wed, Jul 13, 2005 at 09:39:43AM +0100, Steve Hay wrote: > > >>And if we're agreed that leading spaces should be removed from paths on >>the basis that they are very unlikely then perhaps there is no reason to >>treat username and password any differently? Isn't th

Re: metaconfig instructions in Configure out of date?

On Fri, 15 Jul 2005 00:56:59 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > Configure sez: > > # (Note: this Configure script was generated automatically. Rather than > # working with this copy of Configure, you may wish to get metaconfig. > # The dist-3.0 package (which contains metaconfi

RIP OS/2

http://theinquirer.net/?article=24625 BIG BLUE has hammered the final nails into OS/2's coffin. It said that all sales of OS/2 will end on the 23rd of December this year, and support for the pre-emptive multitasking operating system will end on the 31st December 2006. http://www-306.ib

[perl #8765] non-english letters and non-greedy subpatterns, like this one

> [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

Re: [PATCH] Re: [PATCH] was Re: perldoc segfaulting in XS_UNIVERSAL_VERSION

On Fri, 15 Jul 2005 00:49:12 -0700, Michael G Schwern <[EMAIL PROTECTED]> wrote: > 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/un

metaconfig instructions in Configure out of date?

Configure sez: # (Note: this Configure script was generated automatically. Rather than # working with this copy of Configure, you may wish to get metaconfig. # The dist-3.0 package (which contains metaconfig) was posted in # comp.sources.misc and is available on CPAN under authors/id/RAM so # you

[PATCH] Re: [PATCH] was Re: perldoc segfaulting in XS_UNIVERSAL_VERSION

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

Re: [PATCH] Missing tie() call in NDBM_File SYNOPSIS

On Thu, 14 Jul 2005 16:53:03 -0400, Matt Sergeant <[EMAIL PROTECTED]> wrote: > Simple patch for an obvious omission (also fixes the lack of whitespace > on the line before untie()): In this patch I see no whitespace changes at all, nor do I see the need for whitespace changes where you changed i

Re: fchmod, fchown, fchdir

On 14 Jul 2005 15:27:04 -0700, Gisle Aas <[EMAIL PROTECTED]> wrote: > I would like to be able to pass file handles to chmod(), chown() and > chdir() and have perl call the corresponding fxxx() function. This is > similar to how perl treats the argument of stat() or truncate(). > > Below is an im

Re: [perl #21461] perl5.6.1 dos (djgpp) source build broke

On Thu, 14 Jul 2005 20:18:56 -0700, "Michael G Schwern via RT" <[EMAIL PROTECTED]> wrote: > Anybody tried djgpp in a while? I abandoned djgpp looong ago, after several weeks of self-punishment. IMHO it's the most horrible (unix like) development environment I ever had to work in -- H.Merijn

Re: Typo in t/op/stat.t

On 14 Jul 2005 23:20:18 -0700, Gisle Aas <[EMAIL PROTECTED]> wrote: > The $file variable is never used or initialized anywhere else. > This is a fix: Nice catch. Thanks, typo fixed in change #25144 > --- t/op/stat.t.orig 2005-07-14 23:16:52.0 -0700 > +++ t/op/stat.t 2005-07-14 23: