You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has not been fully researched, but there are at least 2 potential ways we could approach this:
Find a similar tool to javacc in .NET that supports similar options that were used in javacc, and create a converter tool to change the javacc configuration into a configuration that the .NET tool supports.
Do a direct port of javacc to C#, and fix its logic to use a more efficient control flow mechanism than exceptions (perhaps goto would be the most direct replacement).
It seems according to this document that using a port of javacc should be our first choice because of the performance benchmarks of the resultant code. And certainly that would eliminate the risk of having a .NET tool not support an option that we need either now or for some future version of Lucene.
The Lucene team is using a tool called javacc to generate the main business logic behind the query parsers. If we had a similar tool it could help:
The javacc tool uses a configuration file as input and creates java code as output. Here are some examples of those configuration files:
This has not been fully researched, but there are at least 2 potential ways we could approach this:
It seems according to this document that using a port of javacc should be our first choice because of the performance benchmarks of the resultant code. And certainly that would eliminate the risk of having a .NET tool not support an option that we need either now or for some future version of Lucene.
JIRA link - [LUCENENET-620] created by nightowl888The text was updated successfully, but these errors were encountered: