Hi, Great idea! It would make Java/Python APIs more manageable as well => we could group related APIs in packages/namespaces.
But have you considered dependencies between the groups? It could be useful for example to be able to define a custom type that is used in two different groups. Regards, Marek From: [email protected] [mailto:[email protected]] On Behalf Of Dave Barach (dbarach) Sent: 28 października 2016 00:02 To: Luke, Chris <[email protected]>; [email protected] Subject: Re: [vpp-dev] Clean-up tasks: 17.01 F0 -> RC0 It's an SMT [simple matter of typing] to create a number xxx.api files, related message handler implementation files, and to place them next to whatever the indicate API collection controls. The current setup is a historical artifact. Thanks... Dave From: Luke, Chris [mailto:[email protected]] Sent: Thursday, October 27, 2016 4:19 PM To: Dave Barach (dbarach) <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: Clean-up tasks: 17.01 F0 -> RC0 Sounds good to me. The api files in particular strike me as unmanageably large right now. I've especially wondered if the API code for each "thing" can move physically closer the "thing" it provides an interface for. Chris. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dave Barach (dbarach) Sent: Thursday, October 27, 2016 4:07 PM To: [email protected]<mailto:[email protected]> Subject: [vpp-dev] Clean-up tasks: 17.01 F0 -> RC0 Folks, I'd like to suggest that we undertake several clean-up tasks once we reach the 17.01 F0 (API freeze) milestone: * Clean up Coverity warnings * Split .../vpp/vpp-infra/{vpe.api, api.c} into groups of related APIs, to reduce future merge collisions * Finish .../vnet coding standards cleanup * Add documentation Thoughts? Thanks... Dave
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
