[asterisk-bugs] [Asterisk 0013357]: AEL doesn't like using dialplan function call as argument for 'jump' statement

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13357 
====================================================================== 
Reported By:                pj
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13357
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 138442 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-21 10:57 CDT
Last Modified:              2008-09-04 08:06 CDT
====================================================================== 
Summary:                    AEL doesn't like using dialplan function call as
argument for 'jump' statement
Description: 
if I try to use function call to return value for jump statement, it fails
due to syntax error below...
if I call jump statement with variable as argument it's working fine

BAD:
jump ${DB(uri/${uri_string})};

OK:
Set(line=${DB(uri/${uri_string})});
jump ${line};

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013416 Function CUT doesn't work if passed as ...
====================================================================== 

---------------------------------------------------------------------- 
 (0092061) murf (administrator) - 2008-09-04 08:06
 http://bugs.digium.com/view.php?id=13357#c92061 
---------------------------------------------------------------------- 
Sorry to take so long to respond; just thought I'd make note that I am
aware 
of this bug; that I intend to fix it; that I know exactly what's going
on,
and have a plan (more or less) on how to fix it; that it will take 1-3
days
of coding, experimenting, testing, etc.

The problem is in the lexical analyzer (flex) spec for 'word'. I need to 
absorb everything between ${ and } without caring what characters they
are.
right now, parens are not allowed in 'word' because it would then absorb
parens
when they are important to recognize as tokens on their own. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-04 08:06 murf           Note Added: 0092061                          
======================================================================