Closed bilsaboob closed 7 years ago
Hey, I changed my mind regarding the ParseContext thingy... lets revisit that in the future in case it's needed... at the moment I'm supporting the GUI with Wrappers around both ParseEngine and ParseRunner - it doen't give "immediate feedback", but good enough at the moment.
Hey,
I've made a couple of minor changes:
Added NonOverlappingIntervalSet collection - in order to build compressed table based DFAs
Made a refactoring to the IParseRunner / IParseEngine interface by adding an IParseContext parameter to the Pulse method - the purpose of this is to act as a "feedback interface", where the internals can log feedback regarding the progress of the parse - mainly in order to support a GUI based "debugger" to display what is going on.
I've considered extending the ParseEngine classes or adding "Events" to the engine, but figured the context version can be useful, allowing several possibilities of overrides without having to care about the internals of the engine - this could be extended further for error reporting and such.