Linked by Thom Holwerda on Tue 7th Sep 2010 21:52 UTC
Permalink for comment 439833
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 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.