winebuild & (name, heap, init)

[Dimitrie O. Paun]

On September 11, 2002 12:06 pm, Alexandre Julliard wrote:
> "Dimitrie O. Paun" <dpaun at rogers.com> writes:
> > Even better -- encode it in the typeinfo.
> >
> > /* M = modifiable */
> > typedef LPSTR LPMSTR;
> > typedef LPWSTR LPMWSTR;
> This way lies madness. The parser shouldn't require any modification
> to the source, and should work on any Windows source, not only the
> Wine ones. 

But I'm not suggesting we generalize this approach. We need this only
for IN/OUT strings. And there are just a few cases where that's so.
If you use LPSTR instead, nothing bad happens, just that during relaying 
you will not see the value of the string going in.

It's just an idea, I don't think it's as bad as you seem it is, but
I'm also not convinced it's worth the trouble. We don't have this feature
right now, and it's not a big deal.

But for the sanity of the discussion, I'll drop it right now. :)

> We shouldn't limit ourselves to what can be extracted automatically
> from the source.

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.

-- 
Dimi.