On Mon, 2009-12-21 at 08:47 -0800, Eric House wrote:
> > Dave Korn <dave.korn.cyg...@googlemail.com> wrote
> > [...]
> > http://blogs.msdn.com/anthonywong/archive/2006/03/13/550686.aspx
> > [...]
> > http://msdn.microsoft.com/en-us/library/bb840031.aspx
> > [...]
> > I believe that's enough publicly-available info for someone to infer the
> > naming scheme from the first one and the constant values from the second and
> > thereby legitimately reproduce the #defines for the header. HTH :)
>
> Helps a ton! I'm unable to find definitions only for the following
> constants:
>
> CONNMGR_PRIORITY_USERBACKGROUND
> CONNMGR_PRIORITY_USERIDLE
> CONNMGR_PRIORITY_EXTERNALINTERACTIVE
> CONNMGR_PRIORITY_LOWBKGND
>
> CONNMGR_FLAG_SUSPEND_AWARE
> CONNMGR_FLAG_REGISTERED_HOME
> CONNMGR_FLAG_NO_ERROR_MSGS
>
> The first set are actually defined at this link:
>
> http://www.studio-odyssey.net/content/note/archive01.htm
>
> which is gibberish to my browser. I suspect it simply pastes in MS's
> copyrighted header file, meaning we couldn't use it.
>
> The second set of three I can't find anywhere (googling for 'define
> <id>').
>
> Actually, as I understand copyright law we *can* use the values from
> the link above. It might be a violation of copyright to
> copy-and-paste from a copyrighted document, but here I'm creating a
> new document using information from another. If MS is claiming the
> values are trade secrets that's another matter. So it seems that
> unless the MS Tools licence prohibits it anyone with a copy of the
> header could look these up and add them.
I have been pointed to the MinGW policy in previous discussions. At , it
says :
> For missing declarations or import functions in the mingw runtime or
> w32api it is essential to specify the source of the documentation on
> which you based your patch, or to otherwise provide proof that you
> have developed your solution through your own experimental effort.
> Never resolve an issue by looking at someone else's work (unless it is
> public domain). We only accept patches based on publicly available
> documentation, (MSDN is an acceptable source, as is any BSD or
> similarly licensed source; no GPL or LPGL licensed source is
> acceptable, unless your patch relates to a MinGW package which is
> already distributed under one of these licences), or on individual
> experimental effort, and never based on others' work, (particularly
> where that work may be proprietary). Note, in particular, that we
> adopt a much stricter standpoint on extracting information from
> Microsoft's SDK headers, than that taken by some other projects, such
> as Wine or ReactOS; consequently we will always reject,
> unconditionally, patches based on information extracted from files
> published by such projects.
so the 'gibberish' URL above looks promising but I'd like to know what
kind of document it is. If it's not copy-pasted from Microsoft SDK
headers then we might be able to use it.
Does anyone understand the language in that page ?
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
