The consensus is that the instance of $new is going to cloned rather than shared. Bummer.. However, I don't see this as a problem yet..

The docs say that open filehandles will be dup-ed so that closing is handled properly. (one doesn't close the other) Although the seek pointer IS shared between the processes.

My problem is still that I have to lock them from reading at the same instant. Now to implement it.

( Keeping in mind I'd really like to stick with default/stock perl modules.)

My first thought is to use semaphores. But I don't see an easy interface such as pop/shift. Or am I making it too complicated. I'll keep working on it.

But if someone would like to chime in with an example of locking processes using semaphores, I'd appreciate it! 8)

Thx, SMF 8)

In reply to Re: (tye)Re: Threading read access to a filedescriptor by smferris
in thread Threading read access to a filedescriptor by smferris

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.