You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Dion Gillard <di...@apache.org> on 2007/10/26 11:11:17 UTC
JEXL 2 Road map
I've gotten JEXL 2 to the point now where it passes all of the 1.1 test cases.
There are a few issues open which were targeted at 2.0 and some others
I've added 2.0 as a Fix For Version in JIRA.
The idea for doing this was to make it easier to change the JEXL code
base, and separate the generated code from the interpretation.
I'd like to 'clean up' some of the following and will raise them as
JIRA issues if others feel they are worthwhile:
- Removal of throws Exception from lots of places in the code and
either use RuntimeException if the exception is going to be ignored or
use the actual exception in the throws clause
- Remove the current JexlExprResolver class and use of pre/post resolvers
- 2.0 API design - this needs some discussion. In particular what
classes should be public in 2.0, package structure etc.
Ideas?
--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
JEXL 2 Road map
Posted by Dion Gillard <di...@apache.org>.
I've gotten JEXL 2 to the point now where it passes all of the 1.1 test cases.
There are a few issues open which were targeted at 2.0 and some others
I've added 2.0 as a Fix For Version in JIRA.
The idea for doing this was to make it easier to change the JEXL code
base, and separate the generated code from the interpretation.
I'd like to 'clean up' some of the following and will raise them as
JIRA issues if others feel they are worthwhile:
- Removal of throws Exception from lots of places in the code and
either use RuntimeException if the exception is going to be ignored or
use the actual exception in the throws clause
- Remove the current JexlExprResolver class and use of pre/post resolvers
- 2.0 API design - this needs some discussion. In particular what
classes should be public in 2.0, package structure etc.
Ideas?
--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.
--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org
Re: JEXL 2 Road map
Posted by Dion Gillard <di...@apache.org>.
Centralised null handling should also be on this list - whether to
gracefully handle null (as is) or allow a new syntax, e.g. velocity
uses $! and groovy uses a? to allow nulls
On 10/26/07, Dion Gillard <di...@apache.org> wrote:
> I've gotten JEXL 2 to the point now where it passes all of the 1.1 test cases.
>
> There are a few issues open which were targeted at 2.0 and some others
> I've added 2.0 as a Fix For Version in JIRA.
>
> The idea for doing this was to make it easier to change the JEXL code
> base, and separate the generated code from the interpretation.
>
> I'd like to 'clean up' some of the following and will raise them as
> JIRA issues if others feel they are worthwhile:
>
> - Removal of throws Exception from lots of places in the code and
> either use RuntimeException if the exception is going to be ignored or
> use the actual exception in the throws clause
> - Remove the current JexlExprResolver class and use of pre/post resolvers
> - 2.0 API design - this needs some discussion. In particular what
> classes should be public in 2.0, package structure etc.
>
> Ideas?
>
>
> --
> dIon Gillard
> Rule #131 of Acquisition: Information is Profit.
>
--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: JEXL 2 Road map
Posted by Dion Gillard <di...@apache.org>.
Centralised null handling should also be on this list - whether to
gracefully handle null (as is) or allow a new syntax, e.g. velocity
uses $! and groovy uses a? to allow nulls
On 10/26/07, Dion Gillard <di...@apache.org> wrote:
> I've gotten JEXL 2 to the point now where it passes all of the 1.1 test cases.
>
> There are a few issues open which were targeted at 2.0 and some others
> I've added 2.0 as a Fix For Version in JIRA.
>
> The idea for doing this was to make it easier to change the JEXL code
> base, and separate the generated code from the interpretation.
>
> I'd like to 'clean up' some of the following and will raise them as
> JIRA issues if others feel they are worthwhile:
>
> - Removal of throws Exception from lots of places in the code and
> either use RuntimeException if the exception is going to be ignored or
> use the actual exception in the throws clause
> - Remove the current JexlExprResolver class and use of pre/post resolvers
> - 2.0 API design - this needs some discussion. In particular what
> classes should be public in 2.0, package structure etc.
>
> Ideas?
>
>
> --
> dIon Gillard
> Rule #131 of Acquisition: Information is Profit.
>
--
dIon Gillard
Rule #131 of Acquisition: Information is Profit.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org