make S_OR and S_COR safe to use even if the parameters are function calls or have...
authorKevin P. Fleming <kpfleming@digium.com>
Thu, 6 Nov 2008 21:09:24 +0000 (21:09 +0000)
committerKevin P. Fleming <kpfleming@digium.com>
Thu, 6 Nov 2008 21:09:24 +0000 (21:09 +0000)
commit433af4241aaf8f2c3c15b98b88976c385a025169
tree5aefc0dcd1c68410b7b7af22805620430337172c
parentf08ab8278c86d084d4d98bef164bb0090dcba674
make S_OR and S_COR safe to use even if the parameters are function calls or have side effects. it still bothers me that these are called S_OR and not something like ast_string_or, but that's water over the bridge

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@155079 65c4cc65-6c06-0410-ace0-fbb531ad65f3
include/asterisk/strings.h