On Wed, Jan 17, 2018 at 2:25 AM, Ole Troan <otr...@employees.org> wrote:
> Hi there,
>
> For a while there has been some interest in making the API language more
> explicit.
> This is a rewrite of the vppapigen generator with support for services {}
> (like grpc), enums, output plugins, better error checking.
>
The change is in:
> https://gerrit.fd.io/r/#/c/8781/
>
> The compiler generates the same output as before. As this has quite a few
> stake holders I will hold off for a week or so awaiting comments before
> asking for it to be published.
>
>
> Future planned features:
> - unions
> - bool, text
> - array support (including length)
> - proto3 output plugin
> - Refactor C/C++ generator as a plugin
> - Refactor Java generator as a plugin
Ole,
Can we add to the "Future Plans" list?
I would like to see it draw a correlation between a message's actual
list of fields and the attempt at a documentation for those fields.
Specifically, there always seems to be some discrepancy and it is
hard to tell which to believe without then going and reading the code.
If the fields and doc lines for the fields at least agreed on which fields
were present, that would be a start.
Thanks,
jdl
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
