2015-06-08 23:33 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
> I know personally, time/resources aside, the biggest reason I have not
> worked a lot on the bigger task (other than my initial work on the new
> query parser) is because I had hoped a solution would present itself to
> Antlr 4 quandary. But it hasn't and likely wont and I think Gunnar and
> Sanne and I are all in agreement that it probably just makes sense to
> this work on Antlr 3.
Sanne? Gunnar? ;)
If we come to the conclusion that tree transformation is vital, then yes, I
don't see another way than going with Antlr3 (see my reply to the other
thread on that). Apart from looking into alternatives to Antlr altogether,
but I don't feel that's a realistic option.
In general, +1 for addressing the parser topic. The changes we have made
for OGM feel a bit ad-hoc-ish to me and I think it makes sense to revisit
this sooner than later to make sure we are (or get) on the right trick.
Wrt. to other agenda items, has Java 8 support been brought up already?
Apart from some "simple" things (like support for Java 8 date/time types),
looking at APIs in the light of Lambdas seems very promising.
Also the criteria API has potential. Things like the already mentioned
QueryDSL or JOOQ seem much nicer on the user wrt. to query creation in a
fluent style. Not sure how we could embrace that, but some usability
improvements in that area would be nice.
hibernate-dev mailing list