[asterisk-bugs] [Asterisk 0013016]: [patch] new CLI commands for handling dialplan variables and name standartization for the old ones

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13016 
====================================================================== 
Reported By:                caio1982
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13016
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 128638 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-07-2008 15:16 CDT
Last Modified:              07-08-2008 13:27 CDT
====================================================================== 
Summary:                    [patch] new CLI commands for handling dialplan
variables and name standartization for the old ones
Description: 
Some commands like 'core set global' should actually be called 'dialplan
set global' as they deal with dialplan variables directly (they even state
that in their help messages), so I decided to change them after commenting
about it on #asterisk-dev. I'm not sure about the consequences of it since
a deprecated warning should be printed, but I will let it to someone more
experienced to decide.

Since there are CLI commands to set new global and per channel variables I
also decided to create equivalent ones to unset these variables as they'd
stay in memory forever until a reload or restart is executed. Not good, now
I can unset them :-)

Ultimately there was not a way to list all those per channel variables set
with 'dialplan set chanvar <channel> <name> <value>', except parsing the
very long output of DumpChan(). I created a command called 'dialplan show
chanvar <channel>', using the same idea from 'show globals' and dumping all
variables associated with the given channel.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 07-08-08 13:27  
---------------------------------------------------------------------- 
I would prefer if you did not provide a facility for unsetting variables. 
There are some fairly nasty things that could happen, especially if you
unset an argument variable (ARG1, ARG2, etc.) or a LOCAL() variable while a
subroutine was executing.

The way the dialplan currently handles this is to set variables to the
empty string, instead, and I would prefer if all such user interfaces used
the same convention. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-08-08 13:27  Corydon76      Note Added: 0089899                          
======================================================================