"Franz Mueller" <[EMAIL PROTECTED]> wrote in message
9kp8hk$[EMAIL PROTECTED]">news:9kp8hk$[EMAIL PROTECTED]...
> But if I write a new syntax highlighter (must be a derived class of
> SynHighlighter class), must I give the source code away? (it's a brand new
> component, but to be accepted by synedit it must be derived from a
> highlighter or I'd have to change SynEdit itself...)
It's a question of the spirit of law vs. letter of law. This could cause a
philosophical debate <g>, but in my opinion, inheritance is a derivative
work, where you modify the original code, even if it's done indirectly.
I hope, we agree that one uses inheritance to "modify" an original class,
otherwise you would use the original class "as is".
MPL gives you the freedom to mix the Original Code with commercial products.
But it's a difference, if you just call MPL function using MPL code as a
"black box", or if you make changes to the MPL code (directly or indirectly)
to improve on it. If you make improvement changes, regardless via direct
code changes or via inheritance, IMHO these changes should go back to the
community, and you should publish them.
I hope that MPL 1.2 will include "inheritance" as a "derivative work ", thus
treating is as a "modification", so this issue would be clear in the future.
My 2c
--
Michael Beck (Team JEDI) http://delphi-jedi.org
http://www.geocities.com/beckmi/delphi.htm
