If I were you, and were a unix man (the two being somewhat redundant), then I'd look at using a sepperate process to that running perl, and using the ptrace system call (probably from C) to periodicly find the curop. You'll have to be able to find the address of the curop variable, which probably means using a perl compiled for debugging. Note that this requires a fair bit of system-specificness (ptrace(2) is documented, on linux, as conforming to a fair number of standards, and being quite system specific. Win32, OTOH, does it's debugging in a completely different way.)
This would allow you to use all the normal methods to sleep, write, whatever. It, however, has a fair bit of slowness associated with 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.
|