Hello! The Freak Parade is using DISQUS, a powerful comment system, to manage its comments. Learn more.
Community Page
- www.thefreakparade.com Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- That's good news, I look forward to reading your posts. Congratulations on the kid cranking. People say things like "I cranked out a few kids" as if it was just another thing, when...
- Thanks so much for the mention, super-flattering of you to say such kind things. Recently I've switched jobs and cranked out some kids, but as of today am back on the blogging bandwagon again!
- I keep a loose eye on NSB to see if parts of what I've done can be reused as NSB components, but in reality while this project started out life as a fork, it really ended up being a nearly...
- Have you thought about merging your changes in with what Udi has done now 1.9 is out the door?
- I'm flattered, but I'm having the time of my life where I'm at :) I've heard great things about Neuron though, I hope to take it for a spin someday.
Jump to original thread »
I have uploaded a new project, Simple Expression Evaluator, to Codeplex. I haven’t had time to create any documentation yet, but as usual the project contains unit tests and a sample application to play with. Simple Expression Evaluator abstracts the the parser+compiler from the
... Continue reading »
10 months ago
Because I would solve this issue with BooParser.ParseString()
10 months ago
I wasn't actually aware of BooParser.ParseString until just this moment. It looks to me, though, like the method gives you an AST tree, which you could then optionally compile and run. This is fine, but I'd still either need to compile the AST tree to my own object model or do a good bit of mucking around with the Boo AST to make sure custom variables were expanded properly, custom functions, etc. I am not sure it would have been any less work at the end of the day, and probably a bit more opaque.
That being said, I'm *not* sure Simple Expression Evaluator has a strong value proposition when compared to the two already existing Expression Evaluators on CodePlex, FLEE (uses dynamic code generation) and LazyParser (uses reflection). Both probably would work as well as mine, and existed before I wrote this. But I wanted a good excuse to try out Irony.net, and I selfishly wanted full control of the API. And, of course, I like this crap, and enjoy the tinkering (something I'm sure you could never understand :) ) Whether or not it provides anybody with a new and better expression eval library (probably not) it can serve as a pretty textbook example of one common approach to turning an AST into an object model and evaluating it.
10 months ago
I wanted to know that you are aware of the other options.