Subject RE: [ib-support] Re: OT: Supercharged Firebird group?
Author Leyne, Sean
> -----Original Message-----
> From: dkuzmenko [mailto:dima@...]
> Sent: Friday, October 04, 2002 3:33 AM


> 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.

We don't!

If that were true, then why do have we maintained the original
Borland/IPL headers in the files?

If that were true, then would we be releasing the changes and new
build/makefiles so that anyone can compile?

Why not?

Because the sources, even converted to C++ are covered by the IPL!

The only module, that I'm aware of, in the engine that is not covered by
the IPL is Dmitry Yemanov's new in memory sort/temp file functions --
this was new work which he created. Of course, the java-driver which is
entirely new work is not convered by the IPL as well.


> As I understand IPL, anyone who provide binaries made
> with the Changed code must make these changes AVAILABLE
> for user of these binaries. I understand that if
> FB Team (or Borland) will buy Yaffil binaries, it can
> demand sources. This doesn't horrible.

Yes, but that means that you should be releasing the IPL covered sources
for/with your existing beta binaries!

You are making binaries available right?


> Returning to the sources - Yaffil can public (or provide)
> 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.

That depends on the methods which are used.

Creating completely new code and then keeping it private, is completely
very game.

Taking code from the existing sources, placing it in a private module
and then modifying it, is not square.


> Why not to include these codepages in FB, to make
> Yaffil and FB more compatible? Any other collaboration
> issues can be discussed freely.

We'd be more than happy for this to happen and eager to work with you
(Yaffil).


--
Sean Leyne

There is nothing wrong with Interbase,
that can't be fixed with Firebird.
http://FirebirdSQL.org