|:h(elp)||Handy for remembering what the shell commands are.|
Leave the shell. The Perl statement exit will work too.
SYNONYMS: :exit, :x
|:set out (D|DD|DDS|Y|P)||
Changes the dumper for the expression results used before
output. The current supported are:
When creating the shell, the dump format is searched among the available ones in the order D, DD, DDS, Y and P. That means Data::Dump is preferred and will be used if available/installed. Otherwise, Data::Dumper is tried, and so on.
Read more about dumpers at Shell::Perl::Dumper.
|:set ctx (scalar|list|void|s|l|v|$|@|_)||
Changes the default context used to evaluate the entered expression.
The default is list.
Intuitively, scalar, s and $ are synonyms, just like list, l, and @ or void, v, _.
There is a nice way to override the default context in a given expression. Just a # followed by one of scalar|list|void|s|l|v|$|@|_ at the end of the expression.
|:reset||Resets the environment, erasing the symbols created at the current evaluation package. See the section ABOUT EVALUATION.|
Remember this is an alpha version, so the API may change and that includes the methods documented here. So consider this section as implementation notes for a while.
In later versions, some of these information may be promoted to a public status. Others may be hidden or changed and even disappear without further notice.
<B>newB> $sh = Shell::Version->new;
Starts the read-eval-print loop after reading options from @ARGV. It is a class method.
The same as run_with_args but with no code for interpreting command-line arguments. It is an instance method, so that Shell::Perl-run_with_args> is kind of:
<B>evalB> $answer = $sh->eval($exp); @answer = $sh->eval($exp);
Evaluates the user input given in $exp as Perl code and returns the result. That is the eval part of the read-eval-print loop.
Prints a list of args at the output stream currently used by the shell.
Outputs the help as provided by the command :help.
Does nothing by now, but it will.
<B>dump_historyB> $sh->dump_history(); $sh->dump_history($file);
Prints the readline history to STDOUT or the optional file. Used to implement experimental command :dump history.
This is experimental code and should change in the future. More control should be added and integrated with other terminal features.
Assigns to the current shell context. The argument must be one of ( scalar, list, void, s, l, v, $, @, _ ) .
Changes current evaluation package. Doesnt change if the new package name is malformed.
Changes the current dumper used for printing the evaluation results. Actually must be one of D (for Data::Dump), DD (for Data::Dumper), DDS (for Data::Dump::Streamer), Y (for YAML) or P (for plain string interpolation).
<B>prompt_titleB> $prompt = $sh->prompt_title; <B>quitB> $sh->quit;
This method is invoked when these commands and statements are parsed by the REPL:
:q :quit :x :exit quit exit
It runs the shutdown procedures for a smooth termination of the shell. For example, it saves the terminal history file.
When the statement read is evaluated, this is done at a different package, which is Shell::Perl::sandbox by default.
$ perl -Mlib=lib bin/pirl Welcome to the Perl shell. Type :help for more information pirl @> $a = 2; 2 pirl @> :set out Y # output in YAML pirl @> \%Shell::Perl::sandbox:: --- BEGIN: !!perl/glob: PACKAGE: Shell::Perl::sandbox NAME: BEGIN a: !!perl/glob: PACKAGE: Shell::Perl::sandbox NAME: a SCALAR: 2
This package serves as an environment for the current shell session and :reset can wipe it away.
There is a lot to do, as always. Some of the top priority tasks are:
o Accept multiline statements;. o Refactor the code to promote easy customization of features.
This project is hosted at Google Code:
To know about interactive Perl interpreters, there are two FAQS contained in perlfaq3 which are good starting points. Those are
How can I use Perl interactively? http://perldoc.perl.org/perlfaq3.html#How-can-I-use-Perl-interactively%3f Is there a Perl shell? http://perldoc.perl.org/perlfaq3.html#How-can-I-use-Perl-interactively%3f
An extra list of Perl shells can be found here:
It is a one-line evaluator by now.
I dont know what happens if you eval within an eval. I dont expect good things to come. (Lorn who prodded me about this will going to find it out and then I will tell you.)
There are some quirks with Term::Readline (at least on Windows).
There are more bugs. I am lazy to collect them all and list them now.
Adriano R. Ferreira, <email@example.com>
Caio Marcelo, <firstname.lastname@example.org>
Copyright (C) 2007X2011 by Adriano R. Ferreira
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
Hey! <B>The above document had some coding errors, which are explained below:B>
Around line 458: Non-ASCII character seen before =encoding in 2007X2011. Assuming UTF-8
|perl v5.20.3||SHELL::PERL (3)||2011-03-12|