gmane.comp.lang.perl.perl5.porters

Re: [perl #43356] magic autogeneration does not work as expected for ++ and --

Marc Lehmann — 2012-05-26T04:49:13

No.


Both readings indicate a bug, because in the example, perl doesn't do any
conversion, and conversions are part of both "all three conversions" and
"everything".

So if the set of operations is "all conversions" or "everything" doesn't
matter, because conversion is part of both sets, and perl uses neither, so
under both interprettaions, perl is buggy.

I think the problem is that, despite me telling you otherwise multiple
times, you think the goal is to have an + or ++ operator overload. I tell
you again: it is not, the goal is to have the conversion operators (and
not + nor ++ nor any other operator), and the documentation is clear on
this even in the section you refer to (and in multiple other places).

The fact that it works with + should be a dead giveaway that something is
wrong, because + isn't overloaded, yet works as documented. ++ does not.

If the goal were to have an overloaded + or ++, it obviously would have to
be implemented (just think about it for a second - you cannot autogenerate
++ f

[perl #9391] return value from 'tied' not discarded soon enough

Father Chrysostomos via RT — 2012-05-26T04:48:15

Thank you.  Applied as 8f9dd74.

[perl #9391] return value from 'tied' not discarded soon enough

Father Chrysostomos via RT — 2012-05-26T04:42:56

I’m surprised which commit fixed it.

$ ../perl.git/Porting/bisect.pl --expect-fail --target=miniperl -e 'use
warnings FATAL=>all;tie < at >a, T;if (tied < at >a) {untie < at >a;}sub T::TIEARRAY {
my $s; bless \$s => "T" }' --start=v5.14.0 --end=v5.16.0
...
dc456155af24d5c772439d33c322bd72cb0fcdfe is the first bad commit
commit dc456155af24d5c772439d33c322bd72cb0fcdfe
Author: Father Chrysostomos <sprout< at >cpan.org>
Date:   Sat Nov 26 18:17:45 2011 -0800

    [perl #97980] Stop tied() from returning a copy
    
    Now tied() returns the actual scalar used to hold the tie object,
    so one can write weaken(tied $foo).

:100644 100644 cc8b099775f98d2fd8933f95f2f5c9039921eed7
78a51aed063dc62d904131416fbe66ed73a7f7b6 Mpp_sys.c
:040000 040000 fdc016fb0933a4351b791c7f362d2432882b5201
bc946781988fe055e105181ef4836117aa806017 Mt
bisect run success
That took 490 seconds

Re: [perl #43356] magic autogeneration does not work as expected for ++ and --

Brian Fraser — 2012-05-26T04:37:36

Aren't you misreading that? To phrase it differently, it says "Of the three
conversion operations, you only need to overload one, and the other two
will be generated from that" not "You only need to overload one of the
three conversions to get everything."

[perl #113090] Data::Dumper -- undef not recognized as "false" in config booleans

Jim Avera — 2012-05-26T04:30:52

# New Ticket Created by  Jim Avera 
# Please include the string:  [perl #113090]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=113090 >



This is a bug report for perl from james_avera< at >yahoo.com,
generated with the help of perlbug 1.39 running under perl 5.12.4.

-----------------------------------------------------------------
Some of Data::Dumper's configuration methods accept "boolean"
arguments.  However passing undef for "false" causes incorrect
behavior (the methods return the old value rather than setting
a new value).

This is not a big deal, but if you want to make them accept undef
as a valid form of "false", here is a patch:

--- Dumper.pm2012-05-26 04:25:18.236706958 +0000
+++ Dumper.pm.ORIG2012-05-25 19:06:41.775175838 +0000
< at >< at > -607,17 +607,17 < at >< at >

  sub Purity {
    my($s, $v) = < at >_;
-  < at >_ >= 2 ? (($s->{purity} = $v), return $s) : $s->{purity};
+  defined($v) ? (($s->{purity} = $v), return $s) : $s->{purity};

Re: [perl #43356] magic autogeneration does not work as expected for ++ and --

Marc Lehmann — 2012-05-26T04:15:42

That's what you claim, but nothing in the documentation supports that,
while the documentation clearly states that implementing 0+ is enough to
get all conversions.

As I wrote before (did you read my mail?) the goal is not to have a full
set of overloaded operations - the goal is to use the built-in ++ and +
operators.

And for that, the documentation section you mentioned clearly says that it
is enough to override 0+ as the other conversion operations are
autogenerated:

       Of the conversions, only one of string, boolean or numeric is
       needed because each can be generated from either of the other two.

So where in the documentation does it say that ++ ignores overloaded
conversion, but + not? The difference is thta + cna force numeric context,
while ++ must be more careful, but the fact that ++ simply ignores
overloading is clearly not documented anywhere in the overload manpage.

Re: Perl secret operators manual page

Kent Fredric — 2012-05-26T02:24:07

For some reason I only know this as "the butterfly operator"

Though oddly, if you search the internet for:   perl "butterfly operator"

The results seem to refer to me.

[perl #19690] make test errors question

Brian Fraser via RT — 2012-05-26T02:23:21

Since Perl 5.8 is long out of support, as is Solaris 5, and seeing how
recent Perls work fine on Solaris 10 & 11, I'm marking this as rejected.
OP, if you are still having issues compiling newer versions of Perl,
please open a new ticket.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=19690

[perl #19716] Error building bleadperl on MSWin32 + Borland CBuilder 3 (bcc 5.3)

Brian Fraser via RT — 2012-05-26T02:18:12

Since we don't support Borland C anymore, I'm marking this as rejected.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=19716

[perl #8965] Tie'd STDIN overwritten by open F, "<-"

Brian Fraser via RT — 2012-05-26T01:58:03

I agree; Moreso since tied filehandles may have nothing to do with
actual file descriptors; e.g. a tied FH with a FILENO method can return
any fileno it wants. So I think this ticket should be rejected.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=8965

Perl 5 Commit Summary

Perl 5 commit summary — 2012-05-26T01:08:10

Perl 5 commit summary, activity since Wednesday

Current branch blead
52 commits.  12 unique authors.  7 unique committers.
70 files changed, 1634 insertions(+), 2676 deletions(-)
Net code removal: Ricardo Signes (1187 lines) Zefram (150 lines)
Thanks, applied:  Father Chrysostomos (6)
Snapshot: http://perl5.git.perl.org/perl.git/snapshot/417a992d4dc78be7.tar.gz

  remove deprecated qw-as-parens behaviour
  Zefram                      11 files changed, 637 insertions(+), 925 deletio
  http://perl5.git.perl.org/perl.git/commit/417a992d4dc78be7

  Block signals during fork (fixes RT#82580)
  Leon Timmermans             2 files changed, 27 insertions(+), 0 deletions(-
  http://perl5.git.perl.org/perl.git/commit/eb3d0a5826dc4202

  fix comparative Perl version numbers
  Zefram                      2 files changed, 2 insertions(+), 2 deletions(-)
  http://perl5.git.perl.org/perl.git/commit/4ea2708986710e97

  perldelta updates
  Zefram                      1 file changed, 51 insertions(+), 1 deletion(-)
  http://

[perl #113088] Data::Dumper::Useqq('utf8') broken [PATCH]

Jim Avera — 2012-05-26T01:06:58

# New Ticket Created by  Jim Avera 
# Please include the string:  [perl #113088]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=113088 >


This is a bug report for perl from james_avera< at >yahoo.com,
generated with the help of perlbug 1.39 running under perl 5.12.4.

-----------------------------------------------------------------
Data::Dumper contains support for encoding non-ASCII characters
as themselves, not \x{...} escapes.  This is controlled by setting
Useqq() to one of the special values 'iso8859', 'utf8', or '8bit'.

The code is commented as "not supported...SUBJECT TO CHANGE".  Fair 
enough. But it's currently completely broken, and I think the fix is 
simple (patch below).

Early in sub qquote() there is the following:

   my $bytes; { use bytes; $bytes = length }
   s/([^\x00-\x7f])/'\x{'.sprintf("%x",ord($1)).'}'/ge if $bytes > length;

This removes all wide characters and the upper half of the
single-octet range bef

[perl #9391] return value from 'tied' not discarded soon enough

Brian Fraser via RT — 2012-05-26T00:47:53

Erm, except that there isn't a test case for it anywhere. My bad.
Attached patch should solve that, THEN this can be closed for good.

--hugmeir


---
via perlbug:  queue: perl5 status: resolved
https://rt.perl.org:443/rt3/Ticket/Display.html?id=9391

[perl #9391] return value from 'tied' not discarded soon enough

Brian Fraser via RT — 2012-05-26T00:39:46

But fixed in 5.16.0; Marking as resolved, although I haven't managed to
find the commit that solved it yet.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=9391

[perl #9528] Bug when testing array returned by sort operator

Brian Fraser via RT — 2012-05-26T00:37:28

Some bikeshedding here: If the warning the applied, I think that it
should be consistent and merely say "Useless use of sort in scalar
context". "dynamic non-array" context is a mouthful, and nothing in the
docs ever refers to something like that; It would only cause more confusion.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=9528

[perl #9637] < at >INC only contains "."

Brian Fraser via RT — 2012-05-26T00:24:12

Are you still experiencing this issue with newer versions of Perl and/or
Apache?

Seeing how this thread has been silent for a while (but not, by a few
weeks, a decade :), I recommend leaving it open for thirty more days,
then closing it unless we get new information or other complains.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=9637

[perl #16930] locale test core dump 5.8.0 release

Brian Fraser via RT — 2012-05-26T00:10:08

Or 5.16.0, for that matter. Seeing how this ticket has been silent for a
few years now, I recommend leaving it open for thirty more days, then
closing it unless we get new information or other complains.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=16930

Re: [perl #37460] system() in threads causes segmentation fault

Leon Timmermans — 2012-05-25T23:51:28

On Sat, May 26, 2012 at 1:10 AM, Brian Fraser via RT
<perlbug-followup< at >perl.org> wrote:

system is defined as non-threadsafe in POSIX, and though our system is
a reimplementation not a delegation I would expect it to suffer from
the same issues (which are plenty but subtle).

Leon

[perl #40382] threads: deadlock occured on creation of a thread while joining others

Brian Fraser via RT — 2012-05-25T23:36:03

I can reproduce the deadlock on 5.8.8, but not on anything newer; I even
tried upping N to 1000, and nothing. Should this ticket be closed?

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=40382

Re: Objects without stashes?

Stevan Little — 2012-05-25T21:36:04

On May 25, 2012, at 10:47 AM, Leon Timmermans wrote:


So, I agree with everything you are saying, and actually this is very similar to the core instance type we are working on in the p5-mop project. If you distill down OO to its very essence you basically need two things. First is an instance type, something that can store instance scoped data, and second is a way to dispatch code (notice I didn't say method here) dynamically to an invocant (which itself is an instance type). Once you have these two things, you can build an entire object system on top of it (class based, prototype based, whatever).

To discuss your specific proposal, to start with, I like it, it removes a chunk of semi-ugly magic we are doing in the p5-mop to get dispatchable objects. I have a few concerns, all of which I think can be worked around.

I think you might run into a circularity issue with fetchmethod and ref being actual methods (how can fetchmethod fetch fetchmethod?), but this is the compromise of bootstrapping, so perhaps y

[perl #37460] system() in threads causes segmentation fault

Brian Fraser via RT — 2012-05-25T23:10:09

Well, I'm not sure if we can close this ticket then. Maybe someone wants
to track it down and write a workaround?

In any case, thank you for the follow up! Much appreciated.

--hugmeir


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=37460