Using compiler error information to check undocumented prototypes and structures?
fracting at gmail.com
Sat Mar 7 09:36:52 CST 2015
On Sat, Mar 7, 2015 at 8:20 AM, Vincent Povirk <madewokherd at gmail.com> wrote:
> At least in MFC headers, public fields are not always documented, and
> many could be considered implementation details. It's not obvious
> where that line should be drawn. And sometimes the headers contain
> inline function implementations, which are effectively part of the
Good point, thanks a lot for the information.
> For projects where "public" means things that are intended to be part
> of the API, maybe this could work, but I'm not aware of any that we
> need to replace.
> Is this about any library in particular?
No, it is not for any particular library, I'm interesting in a general
solution to solve all undocumented situation including mfc and msvcp
and any other libraries. But it is not an urgent task, it's just
something like brainstorm. I was also wondering if writing such a
general tool could be consider a GSoC idea.
More information about the wine-devel