On Sat, Aug 1, 2009 at 2:24 PM, sebb<seb...@gmail.com> wrote: > On 01/08/2009, Rahul Akolkar <rahul.akol...@gmail.com> wrote: >> On Sat, Aug 1, 2009 at 10:10 AM, sebb<seb...@gmail.com> wrote: >> > On 01/08/2009, Rahul Akolkar <rahul.akol...@gmail.com> wrote: >> >> On Sat, Aug 1, 2009 at 12:21 AM, sebb<seb...@gmail.com> wrote: <snip/> >> >> >> >> > The ScriptEngine implementation could even make certain classes of >> >> > global variables read-only, for example System_OUT etc. by disallowing >> >> > changes to them. >> >> > >> >> >> >> <snip/> >> >> >> >> Yeah, making any built-in variables read-only sounds good. >> > >> > For which I think we need a naming convention... >> > >> >> <snip/> >> >> Built-in variables are a bit of a pain (we use them more extensively >> in Commons SCXML as they are required by the spec) so if there is any >> way to avoid having more of them, that'd be good. How about one JEXL >> object that any built-in stuff hangs off? So, JEXL.out would be >> System.out, for example. Extensible in the sense that JEXL.foo and >> JEXL.bar could come along as needed without polluting the vars map >> with more built-in names. > > Nice! > > Sounds good, I'll create an initial implementation. > > Probably OK to use global scope to store it in? > <snap/>
Engine is much safer, IMO. -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
