I don't understand what you meant by far fetched?

Unless you were suggesting the tool should only look for that specific string, the tool would have to know

• That more's output is being piped.
• How more behaves when it's output is being piped.
• The directory from which ls is launched.
• That the file spec will only match the names of file (not directories).
• That ls is given a list of file names (not directories).
• How ls behaves when given a list of file names.

It would also have to make assumptions such as

• sh is used as the shell.
• ls and more aren't aliases.
• ls and more refer to the standard utilities.

All this from a program that's suppose to know Perl. And that's just to handle that one command.

That it will be difficult to pro-grammatically understand the intention? Yes I guess it will

That it requires an incredible amount of knowledge about non-Perl material to have the slightest clue as to the command's meaning.

Regarding @ARGV I would look for 2 or more occurrences of either \$ARGV\[ or shift; outside of any sub or shift @ARGV; and then recommend.

That's no good. Whether you're doing it "correctly" or not, all you have to do with @ARGV is loop over it. The number of times @ARGV is referenced (i.e. how you loop over it) does not indicate how its contents are used at all.

---

---

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.