Hi all,

While working on implementing a new java code gen based on JavaPoet I came 
across one thing that I’m not really happy with.

In BacNet, c-bus, eip and Profinet to we use the 
„generate-properties-for-parser-arguments“ option in the code generation, which 
makes parser arguments available as properties.
This does solve the problem in a hand full of cases. However, does it make the 
code quite ugly.

I was thinking of introducing a new field type „argument“ which you would 
simply give a „name" and it would take the parser arguments type information 
and only output such a field where needed.

This would clean up things and not have these artificial properties generated 
EVERYWHERE (currently they are generated in the parent as well as the children)

What do you think?

Chris

Reply via email to