Re: SE library's licence

Julien PUYDT a écrit :
>> that requires a clean separation of that code. the GPL and LGPL are
>> generally unsuitable for any language that doesn't follow the C model of
>> compilation and linking or is a script language.
> 
> Hmmmm... yes. Each eiffel class lives in its own file, but the generated 
> C code can be joined in a single file. That is an issue. Perhaps asking 
> on some distribution's legal mailing-list (say debian-legal or some 
> such) would be a good idea.

I just had a smart idea: I got hold of gcc's source code, to look at the 
licence of some assembly files. The result is pretty interesting: they 
are covered by... the GPL! But the following is appended just after the 
usual GPL-covering:
  *
  *  As a special exception, if you link this library with files
  *  compiled with GCC to produce an executable, this does not cause the
  *  resulting executable to be covered by the GNU General Public License.
  *  This exception does not however invalidate any other reasons why the
  *  executable file might be covered by the GNU General Public License.
  */

Food for thought,

J.P.