Miki
Miki
Thanks for sharing your ideas. We think as well that it seems there are two different constants: 1. Global Constants - Constants with `const` keyword as we have currently. 1....
We should investigate the possibility of namespace approach as well. Example: ``` namespace Boundaries { subtype uint32 BoundaryWidth; const BoundaryWidth UNKNOWN_BOUNDARY_WIDTH = 0; const BoundaryWidth HIGH_BOUNDARY_WIDTH = 10000; }; ```
We should investigate as well the possibility of change of global constant scope. Constants should not have to be visible before definitions: ``` const uint32 VISIBLE_IN_FOO = 1; struct Foo...
Consider to introduce new command line argument to enable this warning for empty structures as well (see #364).
It is just enough to create warning with new special specifier (tag) for this situation.
Please note that if we decide to change Java Service interface in the suggested way, we should change similarly generated C++ and Python Service interface.
Thank you very much for your post. We like this idea because it will increase the readability of generated code. Because we are busy with grpc just now, we will...
We have implemented documentation comments in the generated code using new command line argument `-withCodeComments`. Documentaion comments in the generated code are disabled by default (`-withoutCodeComments`).
OK. We will put it to the backlog for now.
Python on Windows can clash as well. This is because file names under Windows are case insensitive. Example: ``` const int16 VALUE = 0xDEAD; struct Value { bool hasValue; };...