diff options
author | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-09-07 04:23:00 +0000 |
---|---|---|
committer | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-09-07 04:23:00 +0000 |
commit | b644e296ba2a337f188f89d834381b06fefae102 (patch) | |
tree | 96eaba58a5e3832c4cd2af6f79248170c7a35185 | |
parent | 6a369f9e5337be1a81e302fa2384d1cd36314351 (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: http://svn.digium.com/svn/asterisk/trunk@42224 f38db490-d61c-443f-a65b-d21fe96a405b
-rw-r--r-- | funcs/func_strings.c | 8 |
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, }; |