in reply to Re^4: RFC: IPerl - Interactive Perl ( read-eval-print loop ) (-de_)
in thread RFC: IPerl - Interactive Perl ( read-eval-print loop )

If that is the only thing that is missing to make the debugger worthy of the "REPL" tag, then I really fail to see the problem. I was hoping somebody would be able to explain why "a real REPL" is so much better at being a REPL than the debugger, but I have only seen hand waving and 'x' not being the default. So I consider myself still uninformed (and thus unconvinced).

A patch to allow 'x' to be the default would be interesting. If nothing else, it might trigger explanations as to why it still didn't create "a real REPL".

- tye        

  • Comment on Re^5: RFC: IPerl - Interactive Perl ( read-eval-print loop ) (x)

Replies are listed 'Best First'.
Re^6: RFC: IPerl - Interactive Perl ( read-eval-print loop ) (x)
by BrowserUk (Patriarch) on Dec 20, 2008 at 01:17 UTC

    There are several things that I like about my repl over the debugger:

    1. I can pre-load various useful modules (like List::Util, Benchmark, Math::Random::MT, Data::Dump, threads, threads::shared; Thread::Queue, Win32::API::Prototype) that I use frequently when experimenting.
    2. I have it set up to only evaluate code when a line is terminated with ;; which makes it easier to enter whole subroutines, and loops.
    3. It reports extended error messages ($^E) as well as $!.
    4. I can add new commands and features as I see fit.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
Re^6: RFC: IPerl - Interactive Perl ( read-eval-print loop ) (x)
by LanX (Saint) on Dec 20, 2008 at 01:45 UTC
    Honestly, I think the only full REPL I ever really used was with a BASIC dialect on Atari ST, so I can't tell you what "a real REPL" is. With LISP and Python I'm only a beginner.

    But having to type "x " or "p " each time does in no way compare to the direct feedback of the Python or Ruby command prompt, which I heavily envy.

    Immediate try-and-error experimenting is also very beginner friendly, and I don't see why we should loose fresh blood because of such an (IMHO) easy to realize feature.

    It took me very long to find out how to use the perldebugger as a shell and now I can't understand why there is no automatic x or p !?!

    Cheers Rolf