bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: msvc-inval: more options


From: Bruno Haible
Subject: Re: msvc-inval: more options
Date: Mon, 26 Sep 2011 11:01:42 +0200
User-agent: KMail/1.13.6 (Linux/2.6.37.6-0.5-desktop; KDE/4.6.0; x86_64; ; )

> > Particularlyhttp://bugs.python.org/file12953/__pioinfo.patch
> >
> > A little bit hackhish but seems to work
> ...
> However, it is bad that these data structures can change for every 
> version of MSVC.

Additionally, there's a legal problem here: Code like
  
+#define IOINFO_L2E 5
+#define IOINFO_ARRAYS 64
+       const int i1 = fd >> IOINFO_L2E;
+       const int i2 = fd & ((1 << IOINFO_L2E) - 1);
+               if (0 <= i1 && i1 < IOINFO_ARRAYS && __pioinfo[i1] != NULL) {
+                       if (__pioinfo[i1][i2].osfile & FOPEN)

does not look like something I or you could claim to have written by yourself.
But that is the necessary precondition for code to be contributed to gnulib.
We can't just steal pieces of source code of MSVC's runtime library and
pretend we've written that.

Don't tell me that it doesn't matter because it's less than 10 lines of code.
It most likely has "substantial similarity" with the MSVCRT's sources. Which
is what the lawyers are looking for, when it comes to a copyright lawsuit.

Bruno
-- 
In memoriam Pavlos Bakoyannis <http://en.wikipedia.org/wiki/Pavlos_Bakoyannis>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]