[fpc-pascal] Re: linux: should we hard-code versioned or unversioned shared libraries in our apps?

Reinier Olislagers reinierolislagers at gmail.com
Wed Aug 15 16:08:00 CEST 2012

On 15-8-2012 15:59, Graeme Geldenhuys wrote:
> Hi,
> On 15 August 2012 14:39, Jonas Maebe <jonas.maebe-3RqwKoEL1alVsUKGZV2E3Q at public.gmane.org> wrote:
>>> FCL-DB uses dynamic linking by default, and looks for the unversioned
>>> shared library. So what specific Firebird version is the FCL-DB coded
>>> too?
>> I have no idea, which is why I also said in my first reply:
> Umm, so ideally the ibconnection.pp unit should really be split into
> various units with version numbers in their names. That way we will
> know to which Firebird version they are referring too.
> eg:   ibconnection.pp   // old interbase only (eg: Delphi 7)
>         firebird-1.x.pp
>         firebird-2.1.pp
>         firebird-2.5.pp
> Include files could probably be used to reduce some duplication of code.
OT: that would be useful for another reason.
Firebird 3 will introduce the BOOLEAN datatype and other innovations
(encrypted connections, etc).
Interbase has had BOOLEAN support for a while now.

It would be nice to be able to support new functionality without
sacrificing the ability to connect to older clients.

Of course, this has an obvious parallel to the mysql4....5...6 units;
sorry that I don't know how things are handled there; I've stayed away
from them as much as possible...

More information about the fpc-pascal mailing list