Random thoughts:

* Go multithreaded. Have 10 interpreter threads and a monitor thread. If a particular thread is taking too long at a task, the monitor will kill the thread and start a new one.

* Fork the interpreter children at the beginning and trade data with them via pipes. In your mush's MainLoop, have it check some kind of magic data for the End-of-processing message. If things take too long, send SIGHUP (or something) to the child and have the child kill things.

Implementation details are left up to the reader. These are just ideas :)

In reply to Re: Perlmonks Mush, revisited (Perl as as scripting language) by Kageneko
in thread Perlmonks Mush, revisited (Perl as as scripting language) by BUU

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.