winebuild & (name, heap, init)

[Alexandre Julliard]

"Dimitrie O. Paun" <dpaun at rogers.com> writes:

> But this were I don't agree with you. Experience has shown times and again
> that having a central place where related things sit is better than 
> duplicating the info all over the place. That's why documentation extacted
> directly from source has won. No question about it. May not be perfect, but
> long term is the best solution.
> 
> Now, it is true that we may need some metainfo not present in a bare source
> to do all sorts of nice bells and whistles. But that should be included as
> empty macros or comments in the code, such that we can extract automatically
> all that needs extracting.

Again this works only if you are limiting yourself to the easy
stuff. If you want more than that you have to write actual code, and
you don't want to do that in a function header comments. As for
grouping related things, it's not clear that grouping all relay code
in a single file is worse than spreading it all over the
source. Especially once you start adding more intelligence and
interdependencies between functions and structures.

And of course you don't always have the source in the first place; a
big advantage of keeping it separate would be to do a smart +snoop for
binary dlls.

-- 
Alexandre Julliard
julliard at winehq.com