From @andk

Thanks to Slaven Rezić for bringing this to my attention.

previous ticket already closed

https://rt-archive.perl.org/perl5/Ticket/Display.html?id=119055

diagnostics

http​://www.cpantesters.org/cpan/report/8ad8620c-8942-11e3-8820-3f4d5d7e0655

https://rt.cpan.org/Ticket/Display.html?id=90465

perl -V

  Summary of my perl5 (revision 5 version 19 subversion 3) configuration​:
  Commit id​: 2484f8d
  Platform​:
  osname=linux, osvers=3.10-3-amd64, archname=x86_64-linux-ld
  uname='linux k83 3.10-3-amd64 #1 smp debian 3.10.11-1 (2013-09-10) x86_64 gnulinux '
  config_args='-Dprefix=/home/sand/src/perl/repoperls/installed-perls/perl/v5.19.2-125-g2484f8d/127e -Dmyhostname=k83 -Dinstallusrbinperl=n -Uversiononly -Dusedevel -des -Ui_db -Uuseithreads -Duselongdouble -DDEBUGGING=-g'
  hint=recommended, useposix=true, d_sigaction=define
  useithreads=undef, usemultiplicity=undef
  useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
  use64bitint=define, use64bitall=define, uselongdouble=define
  usemymalloc=n, bincompat5005=undef
  Compiler​:
  cc='cc', ccflags ='-fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
  optimize='-O2 -g',
  cppflags='-fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include'
  ccversion='', gccversion='4.8.2', gccosandvers=''
  intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
  ivtype='long', ivsize=8, nvtype='long double', nvsize=16, Off_t='off_t', lseeksize=8
  alignbytes=16, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags =' -fstack-protector -L/usr/local/lib'
  libpth=/usr/local/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib /usr/lib
  libs=-lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc -lgdbm_compat
  perllibs=-lnsl -ldl -lm -lcrypt -lutil -lc
  libc=, so=so, useshrplib=false, libperl=libperl.a
  gnulibc_version='2.17'
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
  cccdlflags='-fPIC', lddlflags='-shared -O2 -g -L/usr/local/lib -fstack-protector'

Characteristics of this binary (from libperl)​:
  Compile-time options​: HAS_TIMES PERLIO_LAYERS PERL_DONT_CREATE_GVSV
  PERL_HASH_FUNC_ONE_AT_A_TIME_HARD PERL_MALLOC_WRAP
  PERL_NEW_COPY_ON_WRITE PERL_PRESERVE_IVUV
  PERL_USE_DEVEL USE_64_BIT_ALL USE_64_BIT_INT
  USE_LARGE_FILES USE_LOCALE USE_LOCALE_COLLATE
  USE_LOCALE_CTYPE USE_LOCALE_NUMERIC USE_LONG_DOUBLE
  USE_PERLIO USE_PERL_ATOF
  Built under linux
  Compiled at Feb 1 2014 16​:52​:25
  @​INC​:
  /home/sand/src/perl/repoperls/installed-perls/perl/v5.19.2-125-g2484f8d/127e/lib/site_perl/5.19.3/x86_64-linux-ld
  /home/sand/src/perl/repoperls/installed-perls/perl/v5.19.2-125-g2484f8d/127e/lib/site_perl/5.19.3
  /home/sand/src/perl/repoperls/installed-perls/perl/v5.19.2-125-g2484f8d/127e/lib/5.19.3/x86_64-linux-ld
  /home/sand/src/perl/repoperls/installed-perls/perl/v5.19.2-125-g2484f8d/127e/lib/5.19.3
  .

--
andreas

From @demerphq

On 2 February 2014 06​:43, Andreas J. Koenig via RT
<perlbug-followup@​perl.org> wrote​:

# New Ticket Created by (Andreas J. Koenig)
# Please include the string​: [perl #121139]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=121139 >

Thanks to Slaven Rezić for bringing this to my attention.

This is due to​:

commit 2484f8d
Author​: Father Chrysostomos <sprout@​cpan.org>
Date​: Sun Jun 23 07​:08​:24 2013 -0700

  Stop folding of ops from changing mutability

  If $a+$b produces a mutable value, then so should 1+2.

I'm not sure i agree with the assertion in the commit message. But im
only half awake and might change my mind when I wake up :-)

Yves

--
perl -Mre=debug -e "/just|another|perl|hacker/"

The RT System itself - Status changed from 'new' to 'open'

From @rjbs

Yves has declared that this is almost certainly just something for him to update downstream, and that it should not block. I am closing the bug here.

--
rjbs

@rjbs - Status changed from 'open' to 'resolved'