I like to use expressions as property values, i.e.
because I can create different simulation scenarios with a text editor's search and replace function.
Unfortunately, doing this gives an error:
"expected ';' at end of property specification
expected object block closing }"
Using an expression without units is no problem, i.e.
I found the problem in core/load.c in the expression() function: the function interface has a "unit" parameter, but the value of this parameter is never set. The following patch fixes the problem:
===================================================================
--- core/load.c (revision 3850)
+++ core/load.c (working copy)
@@ -1854,7 +1854,13 @@
}
--op_i;}
/ if no semicolon, there's a bigger error, so we don't check that here /
/ postfix algorithm /
/* - while there are input tokens left,
I'll put this into trunk after 3.1 is released.