Ah, you mean to hold the lock for all the child opcodes as well. In that case, the Anonymous Monk already answered

• Sometimes the scope of the CS is too big.

  $shared .= <PIPE>;
  [download]

  would need to be written as

  my $local = <PIPE>;
  $shared .= $local;
  [download]

• Sometimes the scope is too small.

  # XXX. The key and value are related.
  my $string = $shared_key . ' => ' . $shared_value;
  [download]

  won't work without explicit locking.

As you can see, the user still needs to be fully aware of the locking mechanism and must sometimes compensate for it. The only thing accomplished is the removal of the visual cues that something special is happening.

And that's assuming you can figure out where to end the critical section. Consider the following:

• $shared = $shared + 1;
• $local = $shared + 1;
• my $ref = \$shared;
  $$ref = $shared + 1;

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.