[asterisk-dev] new priority of pattern matching in 1.4. Does it makes sense?

[Steve Davies]

On Fri, Feb 22, 2008 at 4:18 PM, Jared Smith <jsmith at digium.com> wrote:
> On Fri, 2008-02-22 at 19:06 +0200, Tzafrir Cohen wrote:
>  > How can it tell there's no exact match in the next included context?
>
>  It won't even look.  Again, once Asterisk finds *any* match in a
>  context, it gives up looking in any other contexts.
>

The current behaviour is fantastic. Please do not change it. It makes
sense, is VERY flexible, and is very well defined in the
documentation.

If you must change it, please make it default to the old behaviour and
add a new flag:

   use_complicated_arbitrary_weighting = yes

And be sure to document all of the thousands of exceptions this will
cause when combining literal, and pattern match, where the literal was
shorter than the pattern match and it was a new moon last Tuesday :)

Just my 2p.
Steve