From e8135ee3d09bb0f05a314bfb395665e29f6b8d99 Mon Sep 17 00:00:00 2001 From: Tilghman Lesher Date: Thu, 1 Sep 2011 17:39:32 +0000 Subject: [PATCH] Merged revisions 334234 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.8 ........ r334234 | tilghman | 2011-09-01 12:38:33 -0500 (Thu, 01 Sep 2011) | 2 lines Remove 1.6 compatibility documentation from 1.8, as it no longer applies. ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/10@334235 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- main/pbx.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/main/pbx.c b/main/pbx.c index 74179f957a..17897ade7f 100644 --- a/main/pbx.c +++ b/main/pbx.c @@ -584,10 +584,9 @@ ASTERISK_FILE_VERSION(__FILE__, "$Revision$") If the variable name is prefixed with __, the variable will be inherited into channels created from the current channel and all children channels. If (and only if), in /etc/asterisk/asterisk.conf, you have - a [compat] category, and you have app_set = 1.6 under that,then - the behavior of this app changes, and does not strip surrounding quotes from the right hand side as - it did previously in 1.4. The app_set = 1.6 is only inserted if make samples - is executed, or if users insert this by hand into the asterisk.conf file. + a [compat] category, and you have app_set = 1.4 under that, then + the behavior of this app changes, and strips surrounding quotes from the right hand side as + it did previously in 1.4. The advantages of not stripping out quoting, and not caring about the separator characters (comma and vertical bar) were sufficient to make these changes in 1.6. Confusion about how many backslashes would be needed to properly protect separators and quotes in various database access strings has been greatly -- 2.47.2