I think the new changes in the expression mechanism broke some past code. This may be by design but I wanted to double-check since the resulting mechanism can get difficult to debug in some cases.
MC allows parantheses without escape characters in calculated values as long as it could parse them. For example I can have tag value:
[bla] =
bla bla bla (more bla)The following expression used to work but now it gives syntax error:
[bla2] = IsEqual([bla], more bla,
Since we do not have direct control of inline functionality, it is weird that [bla] does not return syntax error, but [bla2] returns one. This makes tracking bugs difficult. I recommend that MC either does stronger syntax checking and returns syntax error for [bla] and enforces user to type
bla bla bla /(more bla/) or allows
bla bla bla (more bla) value but converts it to
bla bla bla /(more bla/) internally. I think the latter is better since it is more backwards compatible and easier on novice users.
(I may not be able to followup thread, if you can't replicate please send private message, or email k o n i k @ stanford.edu)