On Tue, 10 May 2016, Michael Schnell wrote:
On 05/09/2016 09:34 PM, Jonas Maebe wrote:
While still missing in the documentation, you can already do that with
{$modeswitch unicodestrings}.
If this avoids the issues, Graeme found, why is this not enabled as default,
as well in the user code
On 05/09/2016 09:34 PM, Jonas Maebe wrote:
While still missing in the documentation, you can already do that with
{$modeswitch unicodestrings}.
If this avoids the issues, Graeme found, why is this not enabled as
default, as well in the user code as in the RTL interface ?
-Michael
__
In our previous episode, Jonas Maebe said:
> > ExecuteProcess is in trunk since late march.
> >
> > It is fairly self contained and could be merged to 3.0.2 technically.
>
> I mentioned that it is in trunk, but it's incomplete: it does not
> translate the command line arguments to the code page
marcov wrote on Tue, 10 May 2016:
In our previous episode, Jonas Maebe said:
As to the original question: most RTL routines don't care about what
the default code page is of ansistrings. Of the ones that do, most
have been adapted to deal with changing the default ansistring code
page (http://
In our previous episode, Jonas Maebe said:
> As to the original question: most RTL routines don't care about what
> the default code page is of ansistrings. Of the ones that do, most
> have been adapted to deal with changing the default ansistring code
> page (http://wiki.freepascal.org/FPC_U
On Tue, 10 May 2016, Graeme Geldenhuys wrote:
On 2016-05-10 09:40, Michael Van Canneyt wrote:
> No idea. As far as I understand pretty much nothing has been done to the
> RTL regarding text encodings, so I wouldn't expect too much.
Why do you say that ?
What would you expect to be done ?
Graeme Geldenhuys wrote on Tue, 10 May 2016:
On 2016-05-10 09:40, Michael Van Canneyt wrote:
> No idea. As far as I understand pretty much nothing has been done to the
> RTL regarding text encodings, so I wouldn't expect too much.
Why do you say that ?
What would you expect to be done ?
By
On 2016-05-10 09:40, Michael Van Canneyt wrote:
>> > No idea. As far as I understand pretty much nothing has been done to the
>> > RTL regarding text encodings, so I wouldn't expect too much.
> Why do you say that ?
>
> What would you expect to be done ?
>
By that I meant a lot in the RTL is sti
On Tue, 10 May 2016, Graeme Geldenhuys wrote:
On 2016-05-10 03:17, Mazo Winst wrote:
1 - So, is there a way to set the codepage to be used by the String type
regardless of the platform?
Yes, apparently via SetMultiByteConversionCodePage(). I still need to
check the documentation to find out
On 2016-05-10 03:17, Mazo Winst wrote:
> 1 - So, is there a way to set the codepage to be used by the String type
> regardless of the platform?
Yes, apparently via SetMultiByteConversionCodePage(). I still need to
check the documentation to find out more details. I think this is what
Lazarus is do
2016-05-09 16:34 GMT-03:00 Jonas Maebe :
> Graeme Geldenhuys wrote:
>
>> Now some would say, simply switch your compiler mode to DelphiUnicode.
>> But I don't want to do that, because I like the stricter ObjFPC mode,
>> and prefer ObjFPC's syntax.
>>
>
> While still missing in the documentation, y
On 2016-05-09 22:48, Sven Barth wrote:
>> > Very good to know. Is that in FPC 3.0.x too, or only FPC Trunk?
> It's also in 3.0.0. In fact it's one of the two modeswitches that has mode
Excellent. That should also fix another issue with FPC 3.x in tiOPF's
D2009+ branch.
function SomeName(const A
Am 09.05.2016 23:38 schrieb "Graeme Geldenhuys" <
mailingli...@geldenhuys.co.uk>:
>
> On 2016-05-09 20:34, Jonas Maebe wrote:
> > While still missing in the documentation, you can already do that with
> > {$modeswitch unicodestrings}.
>
>
> Very good to know. Is that in FPC 3.0.x too, or only FPC T
On 2016-05-09 20:34, Jonas Maebe wrote:
> While still missing in the documentation, you can already do that with
> {$modeswitch unicodestrings}.
Very good to know. Is that in FPC 3.0.x too, or only FPC Trunk?
Regards,
Graeme
___
fpc-pascal maillis
On 2016-05-09 21:14, Tomas Hajny wrote:
> about possible data loss isn't cause by the
> compiler but rather by the user who sets his environment to use a
> character set which can only process a limited subset of all possible
> characters while he intends to use a bigger set.
My issue is with Stri
On Mon, May 9, 2016 21:34, Jonas Maebe wrote:
> Graeme Geldenhuys wrote:
Hello Graeme,
>> Now some would say, simply switch your compiler mode to DelphiUnicode.
>> But I don't want to do that, because I like the stricter ObjFPC mode,
>> and prefer ObjFPC's syntax.
>
> While still missing in the
Graeme Geldenhuys wrote:
Now some would say, simply switch your compiler mode to DelphiUnicode.
But I don't want to do that, because I like the stricter ObjFPC mode,
and prefer ObjFPC's syntax.
While still missing in the documentation, you can already do that with
{$modeswitch unicodestrings}.
17 matches
Mail list logo
