[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-12 13:18 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0107622) pkempgen (reporter) - 2009-07-12 13:18
 https://issues.asterisk.org/view.php?id=15439#c107622 
---------------------------------------------------------------------- 
IMO an empty string is still a valid argument
(the fact that strings are not quoted is a different story)
and thus 'QUOTE()' should evaluate to '""' and
'URIENCODE()' should evaluate to '' (single quotes added
here for clarification).
However I just wanted to point out that there is a difference
in the behavior of these 2 functions even though the syntax in
the documentation is identical (apart from the function name
of course).
Do whatever you like best. It doesn't deserve more time
being dedicated to it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-12 13:18 pkempgen       Note Added: 0107622                          
======================================================================