An
article
about Psh by Gregor N. Purdy you will find in
issue 18 (Summer 2000)
of
The Perl Journal.
In this article the author describes his shell and
also compares it to eight other Perl shells like Larry Walls "
while (<>) { eval; print $@; } "simple shell, the perl debugger,
timtosh
etc.pp.
Probably a good first read about Perl shells.
Line editing: PSH.pm does not support command line editing per se. I'm using WinNT/Win2k and the Command Prompt window provides all command line editing and history features I need. If anyone likes PSH.pm and wants to extend it to optionaly use Term::ReadLine or something, I'm ready to help.
Job Control: Since I'm using (and expecting others to use) PSH.pm usualy for debuging and testing things, then as a real shell I did not consider things like that. Besides ... you have the full power of Perl at your fingertips, you may do whatever you like.
Piping: Any line starting with ! is passed to the default shell for processing. With only one speciality, if the line ends with a > then the output of the command will not be printed but stored in variable $it. Therefore if the default shell supports pipes ...
PSH.pm was never expected to be a real shell. It was more influenced by the interactive development interfaces of Prolog or ML.