Subject | Re: [ib-support] Re: OT: Supercharged Firebird group? |
---|---|
Author | Mark O'Donohue |
Post date | 2002-10-04T22:40:38Z |
Hi Dmitry
dkuzmenko wrote:
(amonst other things)
working on the jbird jdbc driver moved to pure lgpl recently
(previouslty it was dual mpl + lgpl).
Currently for firebird code, Im working off a lgpl + exception clause
for new code I add:
http://firebird.sourceforge.net/rabbits/skywalker/fb_boilerplate.h
Unfortunately (or fortunately depending upon your point of view) I
mainly have worked in the build process, or changing existing code, so
it's not widespread.
However, within Firebird there is a mix of views, a number of the coders
who have worked in firebird prefer an lgpl approach. However Ann for
instance is a keen IPL/MPL supporter (as she says in the article).
The move to C++ generally was for bla-bla-bla C++ features :-). On my
part, mainly the OO stuff, which will hopefully help with reorganising
the code - and a code reformat to make it readable.
Yes, Yaffil team tries to
IPL violations (a lot will violate it quietly anyway) but watch out for
Borland, as someone pointed out to us, if you start making money they
are likely to come after you with a big stick. (mind you it's a long way
to Russia, so you could be safe :-).
In general im impressed the Russian fb/ib/yf community - book and all,
it is obviously quite mature and productive!
Cheers
Mark
dkuzmenko wrote:
(amonst other things)
> Really IPL is a trap. Borland's trap. Firebird groupIPL may not be appropriate for us with new code, for instance those
> trying to avoid it rewriting sources to C++, isn't it?
> You can say words "we don't violate IPL" but don't tell
> me that FB Team rewrote sources to C++ only for using
> exceptions and bla-bla-bla C++ features.
>
working on the jbird jdbc driver moved to pure lgpl recently
(previouslty it was dual mpl + lgpl).
Currently for firebird code, Im working off a lgpl + exception clause
for new code I add:
http://firebird.sourceforge.net/rabbits/skywalker/fb_boilerplate.h
Unfortunately (or fortunately depending upon your point of view) I
mainly have worked in the build process, or changing existing code, so
it's not widespread.
However, within Firebird there is a mix of views, a number of the coders
who have worked in firebird prefer an lgpl approach. However Ann for
instance is a keen IPL/MPL supporter (as she says in the article).
The move to C++ generally was for bla-bla-bla C++ features :-). On my
part, mainly the OO stuff, which will hopefully help with reorganising
the code - and a code reformat to make it readable.
> Returning to the sources - Yaffil can public (or provide):-), It would work, but it *does* make the code hard to read.
> only changes to the code used as a base.
> I.e. since it's based on old C-code (and build) of FB
> it can be hardly compiled, maybe it will be impossible.
> Another way to be saved from IPL is to make all big
> changes as "includes".
Yes, Yaffil team tries to
> be saved from IPL. I can't see any shame here.I don't think we have the money (or the inclination) to go looking for
>
IPL violations (a lot will violate it quietly anyway) but watch out for
Borland, as someone pointed out to us, if you start making money they
are likely to come after you with a big stick. (mind you it's a long way
to Russia, so you could be safe :-).
In general im impressed the Russian fb/ib/yf community - book and all,
it is obviously quite mature and productive!
> And I'm trying to establish collaboration betweenI agree, collaboration is the way to go.
> Yaffil and FB team - there were many cases already,
> and many will be.
>Ouch, hope you make some sales soon.
> Paul, there was not sold any copies of Yaffil yet.
>
Cheers
Mark