On 06/12/2013 05:29 PM, Marco van de Voort wrote:
Yes, and if you chose the explicit compatibility mode for that
version, $mode delphiunicode, it _is_ defined.
Great. I see my concerns about this kind of compatibility seem already
to be cared for.
Thanks !
-Michael
--
On 06/12/2013 05:36 PM, Michael Van Canneyt wrote:
Now why on earth would we do that ? We don't define VERXYZ either in
mode delphi ??
As, String-wise, Delphi (as of version xyz) is not compatible to itself,
IMHO it does make perfect sense to provide the $mode delphiunicode,
additional to
On 06/12/2013 05:31 PM, Marco van de Voort wrote:
No. This is part of that, but only the most initial level. Much is not
yet decided.
... including how compatible it will be. (and more importantly, how
portable the compatibility will be)
As I followed (an took part in) several discussions on
Am 12.06.2013 17:36, schrieb Michael Van Canneyt:
On Wed, 12 Jun 2013, Marco van de Voort wrote:
On Wed, Jun 12, 2013 at 10:55:24AM +0200, Michael Schnell wrote:
On 06/10/2013 08:55 AM, Michael Van Canneyt wrote:
Where is UNICODE defined ?
Isn't the define UNICODE a heritage from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Lazarini.
Thanks for releasing 1.0.10.
On Mac OS X Version 1.0.10 can now also be installed using fink, the debian
like package installer. The choice is between lazarus-aqua, based on a 32-bit
carbon lcl, and lazarus-gtk2, based on a 32 bit
On Thu, 13 Jun 2013, Sven Barth wrote:
Am 12.06.2013 17:36, schrieb Michael Van Canneyt:
On Wed, 12 Jun 2013, Marco van de Voort wrote:
On Wed, Jun 12, 2013 at 10:55:24AM +0200, Michael Schnell wrote:
On 06/10/2013 08:55 AM, Michael Van Canneyt wrote:
Where is UNICODE defined ?
On Thu, 13 Jun 2013, Michael Schnell wrote:
On 06/13/2013 11:32 AM, Michael Van Canneyt wrote:
And they'll need defines anyway because widestring unicodestring on
windows.
The compiler does know whether it compiles for Windows or not. Doesn't it ?
The problem is not in the compiler.
Am 13.06.2013 11:32, schrieb Michael Van Canneyt:
On Thu, 13 Jun 2013, Sven Barth wrote:
Am 12.06.2013 17:36, schrieb Michael Van Canneyt:
On Wed, 12 Jun 2013, Marco van de Voort wrote:
On Wed, Jun 12, 2013 at 10:55:24AM +0200, Michael Schnell wrote:
On 06/10/2013 08:55 AM, Michael Van
On 06/13/2013 11:51 AM, Michael Van Canneyt wrote:
The problem is not in the compiler. The problem is that IF your code
assumes that WideString=UnicodeString
then you will need to differentiate the 2 cases.
I suppose you are correct. But if I understand correctly what my Delphi
addicted
On Thu, Jun 13, 2013 at 11:51:38AM +0200, Michael Van Canneyt wrote:
The problem is not in the compiler.
The problem is that IF your code assumes that WideString=UnicodeString
That is Delphi incompatble. Simply don't enable Delphi compatibility mode
then.
--
On Thu, Jun 13, 2013 at 11:32:36AM +0200, Michael Van Canneyt wrote:
ObjFPC was encountered) and I added the FPC_OS_UNICODE define.
All the more reason not to try to emulate Delphi defines.
Why? We define Windows and MSWindows too?
Maybe not use linux because Kylix does ? :-)
UNICODE
On Thu, 13 Jun 2013, Marco van de Voort wrote:
On Thu, Jun 13, 2013 at 11:32:36AM +0200, Michael Van Canneyt wrote:
ObjFPC was encountered) and I added the FPC_OS_UNICODE define.
All the more reason not to try to emulate Delphi defines.
Why? We define Windows and MSWindows too?
Maybe not
On Thu, Jun 13, 2013 at 09:23:59PM +0200, Michael Van Canneyt wrote:
The problem is not in the compiler.
The problem is that IF your code assumes that WideString=UnicodeString
That is Delphi incompatble. Simply don't enable Delphi compatibility mode
then.
Which Delphi version ?
Any
13 matches
Mail list logo
