Of course the LGPL has a big problem in itself (at least last time I
looked, which was a year ago). The problem is with the using clauses.
They are unclear on one area of code I do a lot of.
I code in C++. As such I have a lot on inline functions (for speed/code
size) defined in header files. So if I have a library that consists of
all inline code (say a C++ template based library). An application
program that uses it would be compiling the code, not just using it.
Maybe this issue has been cleared up in a revision of the LGPL that I
haven't seen yet, and if so please correct me. I am developing a suite
of C++ libraries for linux/Win32 that I currently have a fairly open
license on. I looked into using the LGPL for it, but I scared enough
bussiness lawyers when I showed them the LGPL that I decided against it.
I can't make the applications themselves GPL because various bosses
would shoot me if I made the code that contained nifty little secret
algos public.
Regards,
Steven Roberts
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/