Whatever your problem is, threading support has nothing to do with it. It simply allows you to use use threads to create threads. It has no affect on how system works. If you don't create threads, the only difference with using a threaded build is a performance penalty.

for instance, a system() call creates a file, but the code tries to access the file before the system call is done making it

system won't return until the child exists and therefore after the child is done writing. Processes that don't exist can't write to files, so what you say makes no sense unless the child spawned a detached child and this detached process is actually doing the writing.

In reply to Re: Runing "regular" code with threaded perl by ikegami
in thread Runing "regular" code with threaded perl by kingskot

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.