[asterisk-bugs] [Asterisk 0016451]: core show hints do not follow the general sorting ordre

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16451 
====================================================================== 
Reported By:                RoadKill
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16451
Category:                   Applications/General
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.19 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-16 04:18 CST
Last Modified:              2009-12-18 08:33 CST
====================================================================== 
Summary:                    core show hints do not follow the general sorting
ordre
Description: 
the hints are sorted in the order they are read from the file

====================================================================== 

---------------------------------------------------------------------- 
 (0115425) lmadsen (administrator) - 2009-12-18 08:33
 https://issues.asterisk.org/view.php?id=16451#c115425 
---------------------------------------------------------------------- 
Hmmm, I'm not sure if the order matters there, however, if you're mixing
static (190) and dynamic (_X!) extensions, then I would think the static
should take priority over the dynamic (just like in the regular dialplan).

However, you said you are no longer able to reproduce this? If not, then
I'm going to close this for now, and I'd encourage you to open a new report
if the matching problem you initially saw reappears and you can reproduce. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-18 08:33 lmadsen        Note Added: 0115425                          
======================================================================