CompositeParser initializes in constructor

Question

CompositeParser initializes in constructor

eitch opened this issue 8 years ago · 4 comments

I would prefer it, if the CompositeParser would not call initialize in the constructor, as i want to override the constructor to pass in parameters in sub classes which are then used in the initialize method.

Answer 1 · 2017-04-04T19:28:59.000Z

Do you have a suggestion in how to solve the problem? Lazy-initialization of the composite parser could work, but comes with many complications ...

Could you be more specific in why exactly you need to override the constructor? Maybe there is another solution?

Answer 2 · 2017-04-08T10:27:27.000Z

Possibly the grammar definition approach in Dart could be backported to Java: https://github.com/petitparser/dart-petitparser/blob/master/lib/src/petitparser/definition.dart

Answer 3 · 2017-04-08T18:45:27.000Z

Added GrammarDefinition in f933653, which essentially works the same as CompositeGrammar, but the grammar can be defined anywhere/anywhow. To resolve everything .build() has to be called to get the parser instance. This follows the implementation in Dart and should solve the problem you describe.

Answer 4 · 2017-04-10T06:47:57.000Z

Thanks, i'll have a look at it and migrate to this.