These quick tests can often be done with a
perl -e command
on the command line. However, these can be tedious and the quoting needed
around the Perl code for the shell command line can interfere with quoting
within the Perl code itself. You can also type test code directly into
the input of a simple
perl command and terminate it with a
control-D to signal the end of the input and to run the code.
This, however, forces you to enter all the test code in a raw context
before you can test it. One typo, and you have to type it all in again.
The final option is to create a little test script in an editor to run
to do your testing. If the test is complex enough, this may be the best
option, but there is a significant class of things you may want to test
for which a test script is overkill.
So, it could be handy if Perl had an interactive mode where you could
enter and run Perl code a line at a time in a consistent program
environment. This would be similar to the interactive mode of some
other interpreted programming languages, like Lisp or Scheme, you get by
simply invoking the language interpreter. Perl's debugger serves this
purpose to a fair extent (try it by running
perl -de 0)
and could be used for this sort of quick testing.
However, we might notice that this interactive mode resembles a regular Unix command shell, and call it a Perl shell. Also, it could be useful to be able to run regular Unix commands from within our Perl shell as well as Perl commands. Both types could be intermixed as we desire and we might find it convenient to use our Perl shell throughout our Perl programming session. We could even write scripts for our Perl shell, in our own simple scripting language, mixing Unix commands and Perl commands.
So, with all this heady ambition, let's develop such a Perl shell and
psh. Despite all the functionality we have planned,
we might be surprised how little code it'll take, easily less than a
printed page. Here's an outline of a sequence of steps you might take to
build your program, so you can test and develop your Perl shell in stages
similar to that demonstrated for the haiku
program in class.
'psh> 'before reading each command to prompt the user to enter a line of text.
PSH_PROMPT. If that's not defined or is null, use the default prompt
-soption to your
pshto change the assumption so that such unmarked commands are taken as Unix commands instead.
pshis invoked with a
-hoption. The message should document the features and behavior you've implemented so far and should be updated appropriately at each further stage of development.
:$prompt = 'What is thy command? '.
SHELL, instead of the one you chose in a previous step, to run the Unix commands. If that's undefined or null, use
pshwhich will indicate that the resulting value of any Perl command it evaluates should be printed.
pshwith the input coming from this file. It should run the commands, but still print prompts. Change the program to not print the prompts if the input to the program is not from a user terminal.
psh, besides the hyphen options of course, take the first one to be a script file that
pshshould use as its input and any following ones to be arguments to the script to be used inside the script. These arguments should be stored in an
@argvarray for this purpose. Make sure you don't print prompts if you're running a script (like you don't when the input is not from a terminal). Adapt the file you created in the previous step to be a
pshscript beginning with a
#!line, make it executable, and see if it runs directly as a script like any other script would. If it doesn't entirely work, don't worry -- it seems many operating systems can't handle scripts as script interpreters.
.(sh) command and a
~/.pshrcfile to run upon startup (unless a
-foption is given). You might also implement a
-c commandoption like regular shells have.
Note: Since this is an independent assignment, you must ensure that your program files are not readable by other users on the system. I recommend working on this (and other independent assignments) in a restricted subdirectory of your home directory, created and entered like so:
This program will be due Wed 31 Jan before 11:59pm for full credit. Programs will be accepted up until Thu 1 Feb before 4:00pm at a maximum of 90% full credit. No programs will be accepted after this time. Please submit it via plain text e-mail to
% cd; mkdir a348
% chmod go-rwx a348
% cd a348
Assignment 1in the subject line.
<email@example.com> 24 January 1996