GIT update to branch: master, updated. 6.1-GIT-61-gc6cc0fe

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "HylaFAX".

The branch, master has been updated
       via  c6cc0fe3a48c300fef46dafbfe45c89e59b5bd79 (commit)
       via  fac2aac9cf6c0194f1ba727707193d387ce16313 (commit)
       via  9fb823867f9b6232cee9a56f503f0ec4d41021a1 (commit)
      from  afd94ed9fa99b284ac5c282ab57dd13abb77afc6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c6cc0fe3a48c300fef46dafbfe45c89e59b5bd79
Author: Aidan Van Dyk <[email protected]>
Date:   Mon Aug 29 13:36:38 2011 -0400

    DialRules - recursively allow dialrules to reference others
    
    This allows rules to reference other rules.  The names are looked up
    at runtime, not parse time, so they can reference rules not yet
    defined.  The expected usage would be to reference a "canonicalization" rule
    (either CanonicalNumber directly, or through some indepenant rule) in
    multiple places without needing repeats.
    
    The replace format is of the form be \Name(...)
    
    Example dialrules
        ! rules to canonoicalize numbers to +IDD format
        CanonicalNumber := [
    	....
        ]
        DialString := [
    	.*			= \CanonicalNumber(&)	! Get the canonical
    	^[+]${Country}${Area}	= 			! Local call
    	^[+]${Country}		= ${LDPrefix}		! domestic long distance
    	^[+]			= ${IDDPrefix}		! International
        ]
    
    There is a recursion depth limit in this, just to avoid infinute rule recursion.

commit fac2aac9cf6c0194f1ba727707193d387ce16313
Author: Aidan Van Dyk <[email protected]>
Date:   Fri Sep 9 13:24:09 2011 -0400

    DialRules: Avoid abort on zero length matches
    
    Pattern rules may contain 0 length matches, such as:
       (^[+])?([0-9]*)
    
    We have nothing to replace it with (mlen = 0), so trying to extract
    it from the string causes and abort.  If there is nothing to replace
    it with, there is nothing to try extracting for insertion.
    
    If the match reference was not matched in the string, StartOfMatch and
    EndOfMatch both return -1, leaving mlen = 0, making it an ideal check
    if there is something to extract and insert.

commit 9fb823867f9b6232cee9a56f503f0ec4d41021a1
Author: Aidan Van Dyk <[email protected]>
Date:   Tue Aug 30 16:48:09 2011 -0400

    DialRules: Warn on invalid escape sequence
    
    Instead of just ripping the \ out, make sure we know what the next
    character is and warn if it's not a proper digit.

-----------------------------------------------------------------------

Summary of changes:
 libhylafax/DialRules.c++ |   69 ++++++++++++++++++++++++++++++++++++++-------
 libhylafax/DialRules.h   |    2 +-
 2 files changed, 59 insertions(+), 12 deletions(-)


hooks/post-receive
-- 
HylaFAX


____________________ HylaFAX(tm) Developers Mailing List ____________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null