This process basically has a config file that has a bunch of regexes, and for each regex, an action. Items are passed to the process, and it determines the "best fit" and executes that action associated with it. However, in reading the documentation, it seems that the metric that they use for "best fit" is the pattern with the fewest wildcard characters.

Are you sure the documentation is a correct description of what the code does? (Are you sure you are interpreting it correctly?)

When a given input is able to match two or more distinct regexes in a set (and the chosen action differs for each regex), then there are two ways to choose among the possible paths:

• If the regexes are applied in a specific order and the first one to match determines the action, then there's a simple and unavoidable rule, similiar to the idea in tphyahoo's reply: the regexes need to be ordered from longest specific match to shortest. Otherwise, the longer, more specific regexes would never get a chance to apply.

• If all regexes are tested before any action is taken, and their successes are scored in some way before deciding which action to take, this would provide some flexibility in defining how the scoring works (you could even introduce probabilities, if you wanted results that were non-deterministic but could still correlate in some way with the inputs).

  But for most systems (where people want the results to be deterministic), it's more likely that the best way to score would be based on the length of the match, or rather, the difference between the length of the input and the length of the match. If two regexes yield the same minimum length difference between input and match, then the next criterion might be some sort of ranking among the regexes in terms of their relative literalness or specificity -- e.g. the one using more literals, smaller character classes and/or smaller quantity qualifiers would rank higher. But it's hard to conceive of a programmatic approach to ranking regexes this way.

---

---

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.