This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Gee, everyone, thanks for the support


> > >> You know, I really could care less about this damn WINVER
> thing except
> > >> for the fact that I think that w32api developers are being
> inconsistent.
> > >
> > >I don't even care that much. What annoys me is the [temporary] breakage
> > >to cygwin - which is where the bug report was raised in the
> first place.
> > >
> > >JM2c.
> >
> > Good point.  Earnie, since you're a member of cygwin-developers, why did
> > you allow this to happen?
> >
>
> Christopher January was the person who made the original change.
>
> Christopher Faylor accepted that change.
>
> Someone reported a regression w.r.t. the change.
>
> I checked the MSDN and properly guarded the change as required.

Yep - I was dumb and forgot to use autoload. cgf made an innocent typo
fixing my mistake. This manifested as a missing import. The cause was then
wrongly attributed to the use of a function only present in Windows 2000,
when in fact it was due to cgf's typo. Someone made a fuss about Cygwin
using Windows 2000+ only functions, which doesn't really matter as Cygwin
degrades gracefully when the function is missing (after cgf fixed my
original brain-dead omission to use autoload).
The regression you spoke of was reported *after* cgf's fixed my code to use
autoload and was due to cgf's typo. We all make typos every now and again.

Chris


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]