From svnpenn@gmail.com

Perl 5 currently does not have a REPL that I am aware of​:

https://wikipedia.org/wiki/Read–eval–print_loop

Several other languages offer this, such as​:

- Python
- Ruby
- Julia
- Tcl

I found some workaround, but none of them are ideal. Can use perldebug​:

  perl -d -e 0

but it requires manual printing. Can use eval​:

  perl -E 'while (<STDIN>) {say eval}'

but it fails with pragmas​:

mklement0/perli#3

Can use Devel​::REPL, but it fails with standard input​:

  $ echo 2+3 | re.pl
  $
  $ echo 2+3 | re.pl -
  $
  $ echo 2+3 | re.pl /dev/stdin
  $

Can use "Reply", but no multiline support​:

doy/reply#50

From @leonerd

On Sun, 31 Mar 2019 18​:47​:36 -0700
"Steven Penny \(via RT\)" <perlbug-followup@​perl.org> wrote​:

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

Perl 5 currently does not have a REPL that I am aware of​:

There are many on CPAN; you mention a few, I also created a small one
myself

  https://metacpan.org/pod/App::perlsh

Like Devel​::REPL it doesn't work for stdin, but if that was considered
an important enough feature I could consider adding it. Perhaps send me
a feature request bug against that module.

Either way, however, it's hard to see what there is for core perl to
address here. These are issues with CPAN modules, not core perl itself.

--
Paul "LeoNerd" Evans

leonerd@​leonerd.org.uk | https://metacpan.org/author/PEVANS
http​://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/

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

From svnpenn@gmail.com

Can use Perl 6 as a workaround​:

https://perl6.org

From [Unknown Contact. See original ticket]

Can use Perl 6 as a workaround​:

https://perl6.org

From @Grinnz

On Sun, 16 Jun 2019 17​:39​:35 -0700, svnpenn@​gmail.com wrote​:

Can use Perl 6 as a workaround​:

https://perl6.org

You could also use Python or Ruby, but I hardly see how that's a workaround.