(Resent) Documentation - Reference to MSDN?
octavian.voicu at gmail.com
Thu Jul 1 16:35:37 CDT 2010
On Thu, Jul 1, 2010 at 8:06 PM, Erich Hoover <ehoover at mines.edu> wrote:
> 3) Provide unchanging URLs that can legitimately be used in the source
> code without fear of them changing every week (or being lost forever
> in the case of some older functions)
> 4) Document the ever-growing list of unexpected behaviors that MSDN
> will never tell you about
Why would we want to help Micro$oft with that? How did they ever
contribute to the open source community to deserve that?
As I see it, Wine's primary goal is to aid in the migration from
Windows, a closed platform, to an open platform like Linux. There is
enough to do already (kernel, system dlls, many many libraries,
installer, directx, command line tools, various programs and tools,
testing infrastructure, translations, etc), if we spread ourselves too
thin we won't get anywhere with anything.
Imho there are very few cases in which better documentation would
benefit our cause, but I'm pretty sure that devoting that time to
writing wine code instead of winapi documentation would have a much
PS: there are other resources except MSDN; for example, osronline.com
has very good documentation for windows driver developers, including
some undocumented APIs.
More information about the wine-devel