Linked by Thom Holwerda on Tue 7th Sep 2010 21:52 UTC
Thread beginning with comment 439833
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2007-12-10
Yeah, I agree it's not a clear area. However, if one writes (for example) a C program, and you have
#include "other_lib.h"
You effectively have a derivative work, I would guess, as the C pre-processor has effectively gone and inlined that .h file into your .c file. If the header file was GPL... there could be an argument there.
In any case, I guess the issue would actually have to be tested before a more concrete answer could be found.