On 22/05/2021 07:20, Mark Rotteveel wrote:
> On 22-05-2021 12:03, Dimitry Sibiryakov wrote:
>> 22.05.2021 11:10, Karol Bieniaszewski wrote:
>>> And the final conclusion why new API is better then old one as it was
>>> accepted and preffered.
>>
>>    For application development new API isn't better than old one. Its
>> aim is Firebird plugins development where it has advantage of a single
>> entry point.
> 
> That doesn't match the intent expressed elsewhere in this thread to
> introduce features/types that are only accessible through the new API.
> 

It seems people change what has been said.

I've proposed *to support* the new feature in the legacy API.

And more, in a way it would be very easy to use it, nothing needing a
difficult adaptation to a new version with many things changed together
when incrementing a version (that was never been incremented before).

What I did say I didn't support is to create new-old-API, which things
it already have in a different way it have now.

And actually to be *used directly*, by non C++ code, both APIs are not
easy to use. It's the same with Win32 API, COM API and everything else.

It could have an utility layer on top of it, but I don't think it will
be better than language focused APIs on top of the current new API. I
have been developing (not public) one for C++, supporting tuples,
strings, etc, that for C++ it makes the usage very easy. And it's what
others languages already have too (also on top of old API).

It also must be clear that we're talking about new Firebird features and
the old API is in the way of them, as well not supporting the features
and engineering changes done since v3. It's not in the way because there
is a new API, but because that old API was not good (non extensible, for
example).

So when we talk about fix/reorganize old-API or introduce all new
behavior in it (even when difficult) because people can not (do not want
to) migrate, we are surely throwing away many efforts and doing things
wrongly.

It's also funny that the few who direct uses the old API and do not want
to migrate and asks for core team to maintain it, generally are the ones
constantly asking for new features and fast releases.


Adriano


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to