Solr 4.x和SolrCloud(Solr 4.x and SolrCloud)

 不太确定你在这里尝试了什么，但是如果我要制作一个与单词列表匹配的正则表达式（或者根据具体情况可能是函数名称），我会做类似的事情。 
 
// add/remove allowed stuff here
$allowed = array( 'nl2br', 'substr', 'addslashes' );

// make the array into a branching pattern
$allowed_pattern = implode('|', $allowed);

// the entire regexp (a little stricter than yours)    
$pattern = "/\{function=\"($allowed_pattern)\((.*?)\)\"\}/";

if( preg_match($pattern, $string, $matches) ) {
    # string DOES contain an allowed function
    # The $matches things is optional, but nice. $matches[1] will be the function name, and
    # $matches[2] will be the arguments string. Of course, you could just do a
    # preg_replace_callback() on everything instead using the same pattern...
} else {
    # No allowed functions found
}
 
 $allowed数组使得添加/删除允许的函数名称变得更容易，并且regexp对于大括号，引号和一般语法更加严格，这可能是一个好主意。 
 
 但首先，翻转if..else分支，或使用! 。 preg_match用于匹配字符串中的东西，而不是用于匹配那里不存在的东西。 所以你不能真正让它回归那些不存在的东西 
 
 尽管如此，正如Álvaro所提到的，正则表达式可能并不是解决这个问题的最佳方式，而且无论代码的其余部分如何，将函数暴露出来都是非常危险的。 如果你只是需要匹配单词它应该工作正常，但因为它的函数调用任意参数......好吧。 我不能真的推荐它:) 
 
 编辑：第一次，我preg_quote爆字符串上使用preg_quote ，但这当然只是转义管道字符，然后模式将无法工作。 所以跳过preg_quote ，但是请确保函数名称不包含任何可能搞乱最终模式的内容（例如， 在插入数组之前通过preg_quote运行每个函数名称） 

Not quite sure what you're trying here, but if I were to make a regexp that matched a list of words (or function names as the case may be), I'd do somthing like
 
// add/remove allowed stuff here
$allowed = array( 'nl2br', 'substr', 'addslashes' );

// make the array into a branching pattern
$allowed_pattern = implode('|', $allowed);

// the entire regexp (a little stricter than yours)    
$pattern = "/\{function=\"($allowed_pattern)\((.*?)\)\"\}/";

if( preg_match($pattern, $string, $matches) ) {
    # string DOES contain an allowed function
    # The $matches things is optional, but nice. $matches[1] will be the function name, and
    # $matches[2] will be the arguments string. Of course, you could just do a
    # preg_replace_callback() on everything instead using the same pattern...
} else {
    # No allowed functions found
}
 
The $allowed array makes it easier to add/remove allowed function names, and the regexp is stricter about the curly brackets, quotes and general syntax, which is probably a good idea.
 
But first of all, flip the if..else branches, or use a !. preg_match is meant for, well, matching stuff in the string, not for matching stuff that isn't in there. So you can't really get it to return true for something that isn't there
 
Still, as Álvaro mentioned, regexps probably aren't the best way to go about this, and it is pretty risky to have functions exposed like that, no matter the rest of the code. If you just needed to match words it should work fine, but since it's function calls with arbitrary arguments... well. I can't really recommend it :)
 
Edit: First time around, I used preg_quote on the imploded string, but that of course just escapes the pipe characters, and then the pattern won't work. So skip preg_quote, but then just be sure that function names don't contain anything that might mess up the final pattern (e.g. run each function name through preg_quote before imploding the array)