summaryrefslogtreecommitdiff
path: root/funcs/func_strings.c
diff options
context:
space:
mode:
authorSteve Murphy <murf@digium.com>2006-09-07 04:23:00 +0000
committerSteve Murphy <murf@digium.com>2006-09-07 04:23:00 +0000
commita7b5ef30e7d6c4467690f1124dc4ed11d83ff787 (patch)
tree96eaba58a5e3832c4cd2af6f79248170c7a35185 /funcs/func_strings.c
parent11a7e38930cfc6326963955aaa5481216f01b909 (diff)
With respect to bug 7862, the syntax and description are misleading to users. the syntax included a space after the double quotes between the regex and the data to match. I removed this from the function doc, and added some verbage to make this crystal clear, I hope.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@42224 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'funcs/func_strings.c')
-rw-r--r--funcs/func_strings.c8
1 files changed, 6 insertions, 2 deletions
diff --git a/funcs/func_strings.c b/funcs/func_strings.c
index 3b13d9438..e330738a2 100644
--- a/funcs/func_strings.c
+++ b/funcs/func_strings.c
@@ -142,8 +142,12 @@ static int regex(struct ast_channel *chan, char *cmd, char *parse, char *buf,
static struct ast_custom_function regex_function = {
.name = "REGEX",
.synopsis = "Regular Expression",
- .desc = "Returns 1 if data matches regular expression, or 0 otherwise.",
- .syntax = "REGEX(\"<regular expression>\" <data>)",
+ .desc =
+ "Returns 1 if data matches regular expression, or 0 otherwise.\n"
+ "Please note that the double quotes separating the expression from the data\n"
+ "should not have any neighboring spaces, either before or after, unless you\n"
+ "intend them to be in either the expression or the data!\n",
+ .syntax = "REGEX(\"<regular expression>\"<data>)",
.read = regex,
};