[asterisk-bugs] [Asterisk 0015439]: [patch] URIENCODE() throws a warning when passed an empty string

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15439 
====================================================================== 
Reported By:                pkempgen
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15439
Category:                   Functions/func_uri
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 176029 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-02 00:54 CDT
Last Modified:              2009-07-06 19:05 CDT
====================================================================== 
Summary:                    [patch] URIENCODE() throws a warning when passed an
empty string
Description: 
URIENCODE(${empty}) throws a warning:
WARNING[23535]: func_uri.c:51 uriencode: Syntax: URIENCODE(<data>) -
missing argument!
other functions like
QUOTE(${empty})
don't complain.
====================================================================== 

---------------------------------------------------------------------- 
 (0107436) seanbright (manager) - 2009-07-06 19:05
 https://issues.asterisk.org/view.php?id=15439#c107436 
---------------------------------------------------------------------- 
It is perfectly valid to try and quote or url encode/decode an empty
string.  Also, as there is no way to distinguish between no argument and an
empty argument, I'd lean towards just accepting an empty argument without
warning.  Either way this particular issue doesn't deserve the time being
dedicated to it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-06 19:05 seanbright     Note Added: 0107436                          
======================================================================