It really depends on what you want to achieve with this shell. If you have a reliable shell you want to piggyback then your approach is as good as mine... (except instead of having a regex for each command, do the UNIX modular design: make some small commands and one regex for a whole group of them)
If you want to enhance a shell ( DOS comes to mind ) you need to decide what to emulate. Make some recursive subs that break a command into parts, emulate pipes "|" by openning things with open(PRINTER, "| lpr -Plp1") Perl pipe opens, emulate file io ">","<" with... I guess pipe opens again. To run commands you can have a variable with the directory that contains all the executables, upon command submittal you can check whether the typed command is one of those executables and then run it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|