[asterisk-bugs] [Asterisk 0013339]: AEL parser should trim RHS of an assignment

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13339 
====================================================================== 
Reported By:                dimas
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13339
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-18 18:33 CDT
Last Modified:              2008-09-08 15:27 CDT
====================================================================== 
Summary:                    AEL parser should trim RHS of an assignment
Description: 
When AEL parser parses assignments like
  a = 123;
into
  Set(a=$[ 123]);
that is keeping the leading spaces after assignment operator.
IMHO the leading spaces should be removed:
  Set(a=$[123]);

If one needs to start value with a space, he/she could quote it like:
  a = " 123";

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

---------------------------------------------------------------------- 
 (0092193) murf (administrator) - 2008-09-08 15:27
 http://bugs.digium.com/view.php?id=13339#c92193 
---------------------------------------------------------------------- 
I tried this both in 1.4, and in trunk with app_set=1.6 set, and not set,
and I do not see the problem.

With this in my extensions.ael file:
         my_ext => {
                a= 123 ;
                NoOp(a is '${a}' Isn't it wonderful?);
          }

the generated .conf code:

  '842' =>          1. Set(a=$[ 123 ])                           
[pbx_ael]
                    2. NoOp(a is '${a}' Isn't it wonderful?)     
[pbx_ael]


I see this at run time on the console:

    -- Executing [842 at extension:1] Set("SIP/snom360-082bbb88", "a=123") in
new stack
    -- Executing [842 at extension:2] NoOp("SIP/snom360-082bbb88", "a is
'123' Isn't it wonderful?") in new stack

 The spaces are filtered out by the  $[...] expression.

I'm going to close this bug, but if you feel I have missed the issue,
please re-open and give me more specifics about your configuration. Does
your asterisk.conf have a [compat] section with app_set=1.6? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-08 15:27 murf           Note Added: 0092193                          
======================================================================