Project status

Nov 5, 2014 at 9:45 AM

We've been using Irony to parse expressions for a few years. Thank you.

About time we updated the Irony bits and we're wondering about the status of Irony. I see you're still very active in this forum but the repo hasn't seen any changes in nearly a year. Does that mean you consider Irony "stable" and not needing change or are you engaged elsewhere (VITA perhaps)?

Also, we'd try to use nuget packages as much as possible. I notice that there's a "critical" fix in Dec 2013 that isn't in the current package on nuget. Any chance of an update?

Completely understand is this is just not a focus currently.
Nov 12, 2014 at 8:07 PM
sorry for late response. Yeah, had been busy with VITA and related stuff. This is the main priority, and this is what pays the bills - the company I work at uses it, so this is my highest priority. Plus have a coming presentation at dev conf in December, so trying to round it up and clean the code

I wish I could spend more time with Irony and continue pushing it forward.
I already realize it needs a complete overhaul. The code is outdated (remember "the worst code you ever see is the code you wrote last year"?). If I started it today, I would do it quite differently. But the problem I see is that the whole approach is outdated. The new times bring new challenges. Irony is built on old concepts, created for command-line/batch mode compilers. I modernized the tools and re-implemented LALR automaton using .NET/OOP (BNF-like operator overloading in c#), but the core concepts remain the same - progressive, left-to-right code scanning and quite inflexible parser state automaton. We have now editing with code completion, in Web browser-based editors, and this requires different approaches.
I've been thinking about this for a while and was sketching/prototyping a few things, looking at what it might look like. Unfortunately, in the last few months could not get back to this. The problem is not only the time I have, but the 'thinking energy' - I cannot easily switch contexts. VITA and ORMs and databases take all of my time and energy for now. The problem is not only that it 'pays the bills' but this area (ORMs and databases) is total f-king disaster, EF is a colossal blunder, but so much is at stake here - biz apps that run the economy and everything, need to be written and supported. And this is really screwed up.
Irony, on the other hand, is ok, maybe ugly and outdated but good enough for now. As for future super version - well, don't know. Maybe I'll just publish my random thoughts and invite you folks to chip-in and start prototyping and building the while new shiny thing...
Nuget package - sorry, wasn't really proficient with this, fell out of radar. Just compile the binaries and use them. Not a big deal I hope.
thank you
Nov 13, 2014 at 6:31 PM
No worries. Thank you for the full and frank response. It's appreciated.

I know just what you mean about context switching and paying the bills. What do I expect for free? :)

It is a shame though. This approach, c# only without the need for compiler compilers like Antlr, are very rare.