comment on

The only concern I'd have with this technique is the problem tomhukins described earlier. I'm not sure if what he describes is likely, and whether it's more likely with a read/write filehandle than otherwise, but it's something to consider.

Using a semaphore-like technique (whether it locks the file being modified or another file) also lends itself to situations where your data processing is abstracted away from your data input and output.

Thanks for the example!

Alan

In reply to Re: Re: A flock()alypse now by ferrency
in thread A flock()alypse now by ferrency

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.


Do you know where your variables are?
	PerlMonks