If sb wants in in 2.4.4, I urge you to be quick :-)
Does it mean, that you are preparing release 2.4.4 in short time ?
If yes, then I would happy, if also bug
http://bugs.freepascal.org/view.php?id=16493 with attached patch will be
commited.
Thanks
Laco.
On Tue, 18 Jan 2011, LacaK wrote:
If sb wants in in 2.4.4, I urge you to be quick :-)
Does it mean, that you are preparing release 2.4.4 in short time ?
If yes, then I would happy, if also bug
http://bugs.freepascal.org/view.php?id=16493 with attached patch will be
commited.
I checked
On Tue, 18 Jan 2011, LacaK wrote:
I checked the patch and committed the patch in trunk. Please test and
report, then we can merge the patch to fixes.
The patch is ok, as tested and reported also here
http://bugs.freepascal.org/view.php?id=18114
(and I also use this patch in my
Done. Revision 16776.
Thak you very much.
Could I ask how/when are bugs/patch reviewed/commited ?
Is there any single person(s) who maintains for example fcl-db or any
fpc-developer can apply patches ?
Is there any special time when patches are applied or in trunk can be
patch applied any
In our previous episode, LacaK said:
If sb wants in in 2.4.4, I urge you to be quick :-)
Does it mean, that you are preparing release 2.4.4 in short time ?
More that the process begins. It is at least 3 months between branching and
release, though the third of a series is usually quick.
I just installed MySQL 5.5 and realized that the connector is bound to
5.1. I can see why looking at the code - why this is like that :-)
I had a problem with the usage of $ifdefs all over the place in the code.
It would be worth it since there are so many flavors of MySQL to
re-structure the
In our previous episode, Andrew Brunner said:
It would be worth it since there are so many flavors of MySQL to
re-structure the MySQL component suite to employ the usage of
{$if defined(MySQL50) or defined(MYSQL51) or defined(MySQL55) or
defined(FutureVersions)}
CODE HERE
{$eslif
