I don't think the JexlEngine mutable fields should be made volatile. Same as JexlArithmetic btw.
The intent is not to change them but just to allow configuration of the behavior after the ctor but before usage. In the future, those should also be made final and/or use "feature" ala JexlThreadeArithmetic. This would probably require a JexlEngineBuilder of some sort since the list of options/parameters is pretty long... I'd rather see these setters documented the same (previous) way as in: This method is <em>not</em> thread safe; it should be called as an optional step of the JexlEngine initialization code before expression creation & evaluation. And may be add: Changing them after initialization may result in undefined behavior. -- View this message in context: http://apache-commons.680414.n4.nabble.com/JEXL-New-non-private-mutable-fields-tp4127864p4128517.html Sent from the Commons - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
