On Tue, Dec 02, 2008 at 05:53:54PM +0300, Dmitry Potapov wrote: > Hi Ron, > > > You should probably report this one directly upstream, but before you do, > > please read: http://mingw.org/Reporting_Bugs ... in particular the part > > about them requiring you to provide references to the source of the > > information that you used to create this patch. Without such a reference > > to documentation that we can freely draw from to provide the missing > > symbols you require, I'm afraid they probably won't be able to apply this > > patch. > > A reference to MSDN is sufficient? > http://msdn.microsoft.com/en-us/library/se784sk6.aspx
It used to be, but I'm not sure anymore to be honest. I had heard something some time back about them adding use restrictions to even that. There is a terms of use link at the bottom of that page, but I don't feel qualified to wade through the legalese there and offer an opinion as to what it really allows now. That's why this is best discussed with upstream ;) > As to > __TCHAR_DEFINED -> _TCHAR > _TCHAR_DEFINED -> TCHAR > > I believe it is common knowledge. Yes, but the important question is what is the source of that common knowledge. If that source is not free, then the people who hold this 'common knowledge' are bound by the conditions it was made available to them. Even if they've long since forgotten what those conditions were. > As to the patch, those line of code where not copied from anywhere, > but written by me. Right, I don't mean to impute you with blatant infringement, but the issue is subtle, and the mingw folk do take it quite seriously, so they need evidence of where or how you learned this. As you say this is a relatively common and well known interface, so if it hasn't already been implemented, the big question must be "why not?". The answer may actually be that no one has yet found a sufficiently free source of the information to provide a bona fide clean room implementation. You might just be the first to notice, but doesn't that seem a little odd to you too? I can't answer that, but someone upstream surely can. Since I can't really speak for either them or you, it really is best if you sound them out directly on this. Cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
