Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking reminder for "do EXPR" doc issue #15164

Open
p5pRT opened this issue Feb 7, 2016 · 3 comments
Open

Tracking reminder for "do EXPR" doc issue #15164

p5pRT opened this issue Feb 7, 2016 · 3 comments
Labels
distro-Linux documentation

Comments

@p5pRT
Copy link

p5pRT commented Feb 7, 2016

Migrated from rt.perl.org#127481 (status was 'open')

Searchable as RT127481$
@p5pRT
Copy link
Author

p5pRT commented Feb 7, 2016

From gdg@zplane.com

Created by gdg@zplane.com

This bug report is a tracking reminder for an issue pertaining to the
documentation of "do EXPR" in perlfunc.pod that was debated on the p5p
list over several months last year. It never reached resolution, so I
asked if it made sense to perlbug it as a reasonable way to keep it from
falling in a crack. Steve Hay concurred.

Background​:

The thread arose from a question I had about the example code in perlfunc.pod
"do EXPR", which seemed in need of some repair​:

  http​://www.nntp.perl.org/group/perl.perl5.porters/2015/05/msg227897.html

Summary of follow-on discussion​:

  * Aristotle Pagaltzis responded and agreed that the example was not
  particularly good.

  * We went back and forth a few times on changes to the example, but those
  changes were starting to necessitate wording mods in the surrounding text.
  AP suggested it might be worthwhile to just start from scratch and
  rewrite the entire section. (I concurred.)

  * We took a few shots at it, then some debate ensued (AP, Eric Brine,
  Aaron Crane, Eirik Berg Hanssen). The main point of contention was how
  to properly describe and perform error handling resulting from do EXPR​:
  What conditions should be interpreted as an error; interaction with "1;";
  and interpretation of $! and $@​.

Perl Info 

Flags:
    category=docs
    severity=low

Site configuration information for perl 5.22.1:

Configured by builduser at Tue Dec 15 10:00:24 CET 2015.

Summary of my perl5 (revision 5 version 22 subversion 1) configuration:
   
  Platform:
    osname=linux, osvers=4.3.2-1-arch, archname=i686-linux-thread-multi
    uname='linux flo-32 4.3.2-1-arch #1 smp preempt fri dec 11 07:19:47 cet 2015 i686 gnulinux '
    config_args='-des -Dusethreads -Duseshrplib -Doptimize=-march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong -Dprefix=/usr -Dvendorprefix=/usr -Dprivlib=/usr/share/perl5/core_perl -Darchlib=/usr/lib/perl5/core_perl -Dsitelib=/usr/share/perl5/site_perl -Dsitearch=/usr/lib/perl5/site_perl -Dvendorlib=/usr/share/perl5/vendor_perl -Dvendorarch=/usr/lib/perl5/vendor_perl -Dscriptdir=/usr/bin/core_perl -Dsitescript=/usr/bin/site_perl -Dvendorscript=/usr/bin/vendor_perl -Dinc_version_list=none -Dman1ext=1perl -Dman3ext=3perl -Dlddlflags=-shared -Wl,-O1,--sort-common,--as-needed,-z,relro -Dldflags=-Wl,-O1,--sort-common,--as-needed,-z,relro'
    hint=recommended, useposix=true, d_sigaction=define
    useithreads=define, usemultiplicity=define
    use64bitint=undef, use64bitall=undef, uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
    optimize='-march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong',
    cppflags='-D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include'
    ccversion='', gccversion='5.3.0', gccosandvers=''
    intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234, doublekind=3
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12, longdblkind=3
    ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
    alignbytes=4, prototype=define
  Linker and Libraries:
    ld='cc', ldflags ='-Wl,-O1,--sort-common,--as-needed,-z,relro -fstack-protector-strong -L/usr/local/lib'
    libpth=/usr/local/lib /usr/lib/gcc/i686-pc-linux-gnu/5.3.0/include-fixed /usr/lib /lib
    libs=-lpthread -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc -lgdbm_compat
    perllibs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
    libc=libc-2.22.so, so=so, useshrplib=true, libperl=libperl.so
    gnulibc_version='2.22'
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE'
    cccdlflags='-fPIC', lddlflags='-shared -Wl,-O1,--sort-common,--as-needed,-z,relro -L/usr/local/lib -fstack-protector-strong'



@INC for perl 5.22.1:
    /home/gdg/locperl/lib/perl5/i686-linux-thread-multi
    /home/gdg/locperl/lib/perl5
    /home/gdg/lib/perllib
    /usr/lib/perl5/site_perl
    /usr/share/perl5/site_perl
    /usr/lib/perl5/vendor_perl
    /usr/share/perl5/vendor_perl
    /usr/lib/perl5/core_perl
    /usr/share/perl5/core_perl
    .


Environment for perl 5.22.1:
    HOME=/home/gdg
    LANG=en_US.UTF-8
    LANGUAGE (unset)
    LC_ALL=en_US
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PATH=/home/gdg/bin:/usr/local/bin:/usr/bin:.:/usr/bin/core_perl:/usr/bin/vendor_perl:/opt/bin32-jre/jre/bin
    PERL5LIB=/home/gdg/locperl/lib/perl5:/home/gdg/lib/perllib
    PERL_BADLANG (unset)
    SHELL=/bin/bash

@p5pRT
Copy link
Author

p5pRT commented Jun 5, 2017

From @jkeenan

On Sun, 07 Feb 2016 00​:43​:02 GMT, gdg@​zplane.com wrote​:

This is a bug report for perl from gdg@​zplane.com,
generated with the help of perlbug 1.40 running under perl 5.22.1.

-----------------------------------------------------------------
[Please describe your issue here]

This bug report is a tracking reminder for an issue pertaining to the
documentation of "do EXPR" in perlfunc.pod that was debated on the p5p
list over several months last year. It never reached resolution, so
I
asked if it made sense to perlbug it as a reasonable way to keep it
from
falling in a crack. Steve Hay concurred.

Background​:

The thread arose from a question I had about the example code in
perlfunc.pod
"do EXPR", which seemed in need of some repair​:

http​://www.nntp.perl.org/group/perl.perl5.porters/2015/05/msg227897.html

Summary of follow-on discussion​:

* Aristotle Pagaltzis responded and agreed that the example was not
particularly good.

* We went back and forth a few times on changes to the example, but
those
changes were starting to necessitate wording mods in the surrounding
text.
AP suggested it might be worthwhile to just start from scratch and
rewrite the entire section. (I concurred.)

* We took a few shots at it, then some debate ensued (AP, Eric Brine,
Aaron Crane, Eirik Berg Hanssen). The main point of contention was
how
to properly describe and perform error handling resulting from do
EXPR​:
What conditions should be interpreted as an error; interaction with
"1;";
and interpretation of $! and $@​.

With 5.26.0 out the door, this is probably a good time to bring up this issue again -- but can we start by getting a patch to discuss?

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

@p5pRT
Copy link
Author

p5pRT commented Jun 5, 2017

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

@xenu xenu removed the affects-5.22 label Nov 19, 2021
@xenu xenu removed the Severity Low label Dec 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
distro-Linux documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@xenu @p5pRT