Michael Van Canneyt schrieb:
Simply specify the Delphi version, to which FPC 2.6.1 should be
compatible, then the rest is clear.
There is no such version.
2.6.1 is in many ways D7 compatible, but also has a lot of D20O9
compatible features.
I wonder what in many ways here means?
To the
On Wed, 2 May 2012, Hans-Peter Diettrich wrote:
Michael Van Canneyt schrieb:
Simply specify the Delphi version, to which FPC 2.6.1 should be
compatible, then the rest is clear.
There is no such version.
2.6.1 is in many ways D7 compatible, but also has a lot of D20O9 compatible
02.05.2012 15:00, Hans-Peter Diettrich wrote:
To the user this means not compatible with D7 nor D2009 :-[
It is both compatible with D7 and some D2009 features.
Best regards,
Paul Ishenin.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
On 01.05.2012 17:37, Michael Van Canneyt wrote:
As written before, in MSEgui I'll define a bookmarkty type, so
MSEgui users
have bookmarkty in order to avoid the warning. FPC and Lazarus
probably
can't do the same because of Delphi compatibility. Suggestion:
remove deprecated from
On Wed, 2 May 2012, Martin Schreiber wrote:
On 01.05.2012 17:37, Michael Van Canneyt wrote:
As written before, in MSEgui I'll define a bookmarkty type, so
MSEgui users
have bookmarkty in order to avoid the warning. FPC and Lazarus
probably
can't do the same because of Delphi compatibility.
On 02.05.2012 10:47, michael.vancann...@wisa.be wrote:
For users who do not want to see the deprecated warnings in
fixes_2_6 do
In MSEide+MSEgui:
Use bookmarkty instead of TBookmarkStr for bookmark variables.
In Lazarus:
Use string instead of TBookmarkStr for bookmark variables.
This
Marco van de Voort schrieb:
In our previous episode, Hans-Peter Diettrich said:
The solution is so easy: don't mark it as deprecated.
I also have a clear opinion about Delphi compatibility: Every FPC
version must be compatible to a Delphi version. A mix of incompatible
features from different
On 1 May 2012 23:48, Hans-Peter Diettrich drdiettri...@aol.com wrote:
Simply specify the Delphi version, to which FPC 2.6.1 should be compatible,
then the rest is clear.
In a way I agree here... It is damn confusing when just saying delphi
compatible. Delphi is NOT a product that is standing
On 2 May 2012 09:00, Hans-Peter Diettrich drdiettri...@aol.com wrote:
To the user this means not compatible with D7 nor D2009 :-[
+1000
--
Regards,
- Graeme -
___
fpGUI - a cross-platform Free Pascal GUI toolkit
http://fpgui.sourceforge.net
02.05.12 18:18, Graeme Geldenhuys wrote:
So instead of jumping around with various delphi versions (a bit of D7
and a bit of 2009 etc), maybe start from the oldest delphi version
(eg: D7) and move towards the newest?
Maybe you can teach us how to do this by sending appropriate patches? We
On Wed, 02 May 2012 18:49:13 +0800
Paul Ishenin paul.ishe...@gmail.com wrote:
02.05.12 18:18, Graeme Geldenhuys wrote:
So instead of jumping around with various delphi versions (a bit of D7
and a bit of 2009 etc), maybe start from the oldest delphi version
(eg: D7) and move towards the
On 2 May 2012 13:55, Mattias Gaertner nc-gaert...@netcologne.de wrote:
Please don't feed the trolls.
By no means did I mean to troll. It was a legit statement, and
something that confuses the hell out of FPC developers like myself.
For example: tiOPF branched off version 3 so as to support
On Wed, May 2, 2012 at 5:47 AM, michael.vancann...@wisa.be wrote:
On Wed, 2 May 2012, Martin Schreiber wrote:
On 01.05.2012 17:37, Michael Van Canneyt wrote:
As written before, in MSEgui I'll define a bookmarkty type, so
MSEgui users
have bookmarkty in order to avoid the warning. FPC and
02.05.12 21:32, Graeme Geldenhuys wrote:
Maybe the FPC core team will be so kind as to create a new FPC
features since xxx page on the wiki (similar to what I have done for
Lazarus).
From the anouncement of FPC 2.6.0 which was posted to this mail list:
Changes that may break backwards
On 02.05.2012 15:41, Marcos Douglas wrote:
This last one is bad advice, this code will break as soon as they switch to
2.6.3. Which, presumably, eventually they will.
If you really want to avoid the messages, it is better to use TBookmark,
GetBookmarkData and FreeBookmark.
That will not
Mattias Gaertner ha scritto:
On Wed, 02 May 2012 18:49:13 +0800
Paul Ishenin paul.ishe...@gmail.com wrote:
02.05.12 18:18, Graeme Geldenhuys wrote:
So instead of jumping around with various delphi versions (a bit of D7
and a bit of 2009 etc), maybe start from the oldest delphi version
(eg:
Giuliano Colla giuliano.co...@fastwebnet.it hat am 2. Mai 2012 um 17:21
geschrieben:
Mattias Gaertner ha scritto:
[...]
This is starting to become off-topic.
[...]
Breaking compatibility is something very similar to leaving an old lady
in the middle of the road.
Now it's off topic.
On Wed, May 2, 2012 at 11:47 AM, Martin Schreiber mse00...@gmail.com wrote:
On 02.05.2012 15:41, Marcos Douglas wrote:
This last one is bad advice, this code will break as soon as they switch to
2.6.3. Which, presumably, eventually they will.
If you really want to avoid the messages, it is
On 2 May 2012 15:59, Paul Ishenin paul.ishe...@gmail.com wrote:
...
Details about these new features can be found at
http://wiki.freepascal.org/FPC_New_Features_2.6.0
Thanks Paul. I didn't know (or forgot) about these links. This would
be helpful in creating a wiki matrix page of FPC vs
Tomas Hajny schrieb:
On Wed, May 2, 2012 12:27, Hans-Peter Diettrich wrote:
Marco van de Voort schrieb:
In our previous episode, Hans-Peter Diettrich said:
The solution is so easy: don't mark it as deprecated.
I also have a clear opinion about Delphi compatibility: Every FPC
version must be
Paul Ishenin schrieb:
02.05.12 18:18, Graeme Geldenhuys wrote:
So instead of jumping around with various delphi versions (a bit of D7
and a bit of 2009 etc), maybe start from the oldest delphi version
(eg: D7) and move towards the newest?
Maybe you can teach us how to do this by sending
21 matches
Mail list logo
