Thanks, Matt. Yes, I've been working around it by just adding "+0" to path expressions that end in a parentheses. I hadn't quite figured out that it required starting with a non-matched parentheses to trigger the error; it's good to know exactly what circumstances cause it to arise. A suggestion for Bruce--ifeffit flags these kinds of syntax errors pretty well. Is it possible for Artemis to look at the ifeffit output and alert the user to examine the iffefit output if there is an error? --Scott Calvin Sarah Lawrence College At 09:33 AM 6/7/2005 -0500, you wrote:
Hi Scott,
Yep, that is an ifeffit error. It turns out to be specific to math expressions in path() commands, but it is definitely a bug. It seems that a math expression for a path parameter that starts with '(' and ends with ')' and for which these '(' and ')' are not a matched pair will incorrectly raise a syntax error. This doesn't happen for set() or def().