Danny Smith wrote:
> > ----- Original Message -----
> > From: "Casper Hornstrup" <chorns@...>
> > To: <mingw-patches@...>
> > Sent: Friday, 9 August 2002 23:57
> > Subject: [MinGW-patches] [PATCH] Windows Sockets Helper definitions
> > I find it a bit confusing. As you say this is documented in the DDK
> > documentation,
> > but this file is not located in the MS Windows DDK. It comes with the
> > Platform SDK.
> It is a recent addition. It was not in Nov 2001 version of PSDK, which
> makes it even more confusing.
> > The Platform SDK contains more than the Win32 API, so maybe we should
> > if
> > w32api should be a platform SDK or we should have a new subproject for
> > additions that isn't strictly Win32 APIs. Other Windows Sockets files
> > be more
> > Platform SDK material than Win32 API material. Also DirectX is really
> > Win32 APIs
> > either. I vote for a new CVS module for the non-Win32 API stuff.
> > Casper Hornstrup
> That means that 'someone' is going to have to decide what is w32api and
> what is something else. It could also lead to time-wasting
> to-and-froing on this list trying to agree where a particular component
> should go unless 'someone' actually commits to taking the
> buck-stops-here responsibility for these decisions.
> As you say the distinction is not always clearcut.
> For the nonce, I have no objection to your patch going into the w32api
> package. Perhaps a short comment at the top of header about the fuctions
> being documented in DDK. If no else has any objection, I will check in.
> A classification of the components in the w32api as it it exists now
> would be useful (something along the lines of the w32api.csv file that
> is distributed with MS PSDK, but in friendlier format) It could be
> included as a part of distro. Once that is done, we could review if or
> how we want to split things up.
I read this post after creating the winsup/w32sdk. I don't have a clear
opinion on this matter. I'm sitting on the fence at the moment and
could fall either direction. However, I'm thinking that regardless of
MS doings, if the documentation support it in w32api that is where it
belongs. Otherwise it belongs in a separate package, i.e.: w32sdk. So,
the deciding factor will be, "where does the documentation put it?".