Hey,
Does anyone on this list have experience writing parsers in Java? To
give a little background to that question, I'm considering (and have
been for a while) replacing Stripes' use of OGNL with a custom
expression parser/executor. Given how Stripes uses OGNL, I'm fairly
convinced at this point that I could write an entire expression
evaluator in less code than I now have to push and coerce OGNL into
doing what I want it to do! And it would probably be a *lot* simpler
since it could be structured to solve exactly the use cases that
Stripes needs instead of being the worlds largest (and most poorly
documented) swiss-army knife ;)
So I'm thinking I might try and POC this over the next week, and the
one area that I'm not terribly familiar with is the best way to write
a parser for an expression language. It needn't be very complex at
all. I think it basically needs to support
- nested property syntax (foo.bar.splat)
- numeric indexed property syntax (foo.bar[12].splat)
- map indexed property syntax (foo['bar'].splat
In fact it'd probably just be a subset of the new Unified EL grammar
to be consistent. Anyone have good suggestions on the easiest way to
create a parser for an EL?
-t
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
