Since you asked for comments... :)
Bullet 1: To avoid calling a sub you could use a do {} block after the or. This way you don't have to worry about the return value and you can still add to that section of code (better error-checking, etc.)
Bullet 2: agreed
Bullet 3: In part I agree with your reasoning here, and where it applies to what you do, it's certainly a valid approach. I think you'll find, though, that other perl programmers will expect the idiomatic example in place of a more elaborate one. Especially when demonstrating an unrelated construct (reading piped output, in this case) it may be unnecessary to allow for growth of the example, and simplicity might be preferred. At the same time, I don't think your example was at all unclear, so it's really a matter of taste.
...what happened to my point? I could've sworn I had one when I started writing this. ;)
-BirdIn reply to Re: Re: Re:x2 External program with large amounts of output
by Bird
in thread External program with large amounts of output
by cyberconte
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |