in reply to Re^2: Using Devel::REPL
in thread Using Devel::REPL

Strange indeed, it works for me. Are you sure reply runs the correct executable?

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

Replies are listed 'Best First'.
Re^4: Using Devel::REPL
by guiwp (Sexton) on Jun 23, 2016 at 12:16 UTC
    guilherme@debian:[~]: grep -m1 -e version $(which reply) version 0.35 guilherme@debian:[~]: md5sum $(which reply) 4187760e3097dd0d0e68eab89a043c6f /usr/bin/reply guilherme@debian:[~]: file $(which reply) /usr/bin/reply: Perl script, ASCII text executable guilherme@debian:[~]: dpkg -S $(which reply) libreply-perl: /usr/bin/reply guilherme@debian:[~]: apt-cache show $(echo $(dpkg -S $(which reply))| +cut + -d: -f1) Package: libreply-perl Version: 0.35-1 Installed-Size: 196 Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debia +n.org> Architecture: all Depends: perl, libconfig-ini-reader-ordered-perl, libdevel-lexalias-pe +rl, libeva + l-closure-perl (>= 0.11), libfile-homedi +r-perl, libmodule-runtime-perl, libpacka + ge-stash-p +erl, libpadwalker-perl, libtry-tiny-perl Suggests: libapp-nopaste-perl, libb-keywords-perl, libcarp-always-perl +, libclass + -refresh-perl, libdata-dump-perl, libdat +a-printer-perl, libmro-compat-perl, libp + roc-invoke +editor-perl, libterm-readline-gnu-perl Description-en: lightweight extensible Perl REPL Reply ("read, eval, print, loop, yay!") is a lightweight, extensible +REPL for Perl. It is plugin-based (see Reply::Plugin), and through plugins sup +ports many advanced features such as coloring and pretty printing, readline support, and pluggable commands. . NOTE: This is an early release, and implementation details of this mo +dule are still very much in flux. Feedback is welcome! Description-md5: d625336bcf21da688357d76480cd6070 Homepage: https://metacpan.org/release/Reply Tag: devel::lang:perl, devel::library, implemented-in::perl Section: perl Priority: optional Filename: pool/main/libr/libreply-perl/libreply-perl_0.35-1_all.deb Size: 83562 MD5sum: 98770e9cf54c5b3566eb272739904279 SHA1: 0fa6baec41dfc19dede44ab73ff230c3448cf4e5 SHA256: 0cd536376f11068191dea6fbbd287e7ff01451c3263702990f5e6cf8d94f18 +12
      Hello guiwp,

      This is very strange - I can see for certain that --cfg option is available in reply-0.35 and it even worked on my latest install with --cfg. So, I'm not sure what the problem is with your install -- can you check with your debian package maintainer?

        My test cases were:
        1. I've noted that if I just run reply without arguments and in its shell type "use mymodule" it just works fine.
        2. If I run any installed module (reply -M Data::Dumper) works fine
        Maybe somehow my module/script is interfering with the logic of the reply... I'll comment out some lines and see if things change.

        Here is header of my simple module:

        #!/usr/bin/env perl package Wik; use v5.20.2; use strict; use warnings; use open qw/:std :utf8/; use utf8; use MediaWiki::Bot qw(:constants); use Data::Dumper; use YAML::Tiny; use Path::Tiny qw(path); use Getopt::Long; use HTTP::Date; use Pod::Usage; use URI::Escape; require Exporter; our $VERSION = 0.2; our @ISA = qw(Exporter); our @EXPORT = qw(login savepages updatepages);
        Thank you @robby_dobby, I'll dig in my little code and try to see if I'm doing something wrong...