On Tue, December 2, 2014 08:31, Hans-Peter Diettrich wrote:
> Jonas Maebe schrieb:
>
>> To get behaviour that is compatible with Delphi2009+, compile with
>> -Mdelphiunicode or {$modeswitch delphiunicode}.
>
> Do you mean {$mode delphiunicode}?
>
> Now I wonder about compilation at all.
> When I co
On Tue, 02 Dec 2014 04:05:59 +0100
Hans-Peter Diettrich wrote:
> Jonas Maebe schrieb:
> >
> > Hans-Peter Diettrich wrote on ma, 01 dec 2014:
>
> > To get behaviour that is compatible with Delphi2009+, compile with
> > -Mdelphiunicode or {$modeswitch delphiunicode}.
>
> The compiler option (-M
On Tue, 2 Dec 2014 09:18:29 +0100
"Tomas Hajny" wrote:
>[...]
> Probably best to ask about the wrong behaviour with Lazarus on a Lazarus
> list? Otherwise: In what format (encoding) is your source file? Unless
> it's a UTF-8 with BOM, FPC decodes it according to the -Fc parameter and
> Lazarus ma
On Tue, 02 Dec 2014 04:05:59 +0100
Hans-Peter Diettrich wrote:
>[...]
> BTW it's nice that FPC console Write/Ln (mostly) converts AnsiStrings to
> the console codepage, while Delphi (XE) doesn't convert :-)
+1
Although it confuses people who don't know about "console
codepage" (OEM codepage).
Tomas Hajny schrieb:
On Tue, December 2, 2014 08:31, Hans-Peter Diettrich wrote:
When I compile a console program on the commandline, most strings are
readable in the console (see previous answer). But when I compile using
Lazarus, all strings (including UnicodeString!) are shown in unreadable
Mattias Gaertner schrieb:
On Tue, 02 Dec 2014 04:05:59 +0100
Hans-Peter Diettrich wrote:
Many things affect string literals. Source codepage, system codepage,
string type, defaultsystemcodepage, library, compiler version.
I started a table for UTF-8 literals:
http://wiki.lazarus.freepascal.o
you can find a lot of information on CMSIS here:
http://www.arm.com/products/processors/cortex-m/cortex-microcontroller-software-interface-standard.php
To download the svd-files you need to create a free account @arm.com,
then you can download lots of svd files for all major chips.
It is even
On 11/28/2014 09:15 PM, Hans-Peter Diettrich wrote:
You suggested to use "string" as UTF-16 on Windows, and UTF-8 on
Linux. That's what I understand as a unique program-wide string
representation (not sourcecode-wide, instead program as *compiled*).
Then I cannot see any need or use for anoth
On Tue, 02 Dec 2014 11:32:13 +0100
Hans-Peter Diettrich wrote:
> Mattias Gaertner schrieb:
> > On Tue, 02 Dec 2014 04:05:59 +0100
> > Hans-Peter Diettrich wrote:
>
> > Many things affect string literals. Source codepage, system codepage,
> > string type, defaultsystemcodepage, library, compiler
On 12/02/2014 01:05 PM, Michael Schnell wrote:
But why do you say "would be appreciated" ? Is it not possible to use
"RawByteString" in a way the name suggests, by never bringing it
together with any String variable of a different encoding brand and
hence avoid any conversion - be same intentio
On 11/29/2014 07:55 AM, Jonas Maebe wrote:
Exactly the same goes for converting strings with code page CP_NONE to
a different code page: your program is broken when it tries to do that,
While accessing an array beyond its bounds is not detectable at compile
time and accessing an array beyond i
On 11/29/2014 05:36 PM, Hans-Peter Diettrich wrote:
As Delphi doesn't allow for a dynamic encoding of CP_NONE, I don't
understand the purpose of the FPC description.
As you suggested in the other mail, the Delphi implementation of
RawByteString is decently flawed and this supposedly is introduc
On Tue, 02 Dec 2014 13:31:44 +0100
Michael Schnell wrote:
>[...]*defined* *to* *be* *undefined*
Ooh, that is soo meta. lol
Mattias
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
On 11/28/2014 08:19 PM, Hans-Peter Diettrich wrote:
In that discussion I found several errors, which are not detected by
the compiler nor handled in the RTL. In the concrete entry the illegal
use of the *generic* CP_NONE identifier is mentioned. That's why I
felt a need to address several spe
i wasn't able to figure this out but i did make it a little further after i
updated all the .O and .ppu files in the trunk/units/i386-win32/fcl-base
directory... the next error was
=== snip ===
Start compiling package utils for target i386-win32.
Compiling BuildUnit_utils.pp
Com
Michael Schnell schrieb:
On 11/29/2014 07:55 AM, Jonas Maebe wrote:
Exactly the same goes for converting strings with code page CP_NONE to
a different code page: your program is broken when it tries to do that,
While accessing an array beyond its bounds is not detectable at compile
time and a
Michael Schnell schrieb:
On 11/28/2014 09:15 PM, Hans-Peter Diettrich wrote:
Apart from that, every encoding-tolerant code will execute much slower
than code without a need for checks and conversions everywhere.
As I pointed out I don't agree at all.
- The check is only two ASM instructions
17 matches
Mail list logo
