On 01/11/2011 11:10 AM, Hans-Peter Diettrich wrote:
UTF-8 combines an single (byte-based) storage type with lossless
encoding of full Unicode. Ansi and UCS2 (really UTF-16) only *look*
easier to handle in user code, but both will fail and require special
code whenever characters outside the
Matt Emson wrote:
I would also agree. I used to use Interfaces or raise shared
classes/declarations to a new unit both could use to overcome this
issue myself. But I remember the Be GUI porters having loads of issues
mimicing the Be API header structure because there were so many
forward
Michael Schnell wrote:
Again something inspired by Delphi-Prism ?
( http://prismwiki.codegear.com/en/Lambda_Expressions )
Wow, talk about unreadable code...
I'm all for saving typing, but not at the expense of readability. This
reminds me of C's oddball ? operator. One of the reasons I
Martin Friebe wrote:
I must agree with the FPC can not to it all automatically line (as
much as I regret, and admit the beauty there was, if fpc could).
What I mean is:
1) Any Application/Program, that currently compiles and works (using
none utf8, never mind if ascii or ansi) will keep
Micha Nelissen wrote:
I'm using an XScale armeb (big-endian) debian distribution here at work.
The DigiConnect ME and WI-ME modules run ARM7 big endian as well. Not
sure about the other Digi modules. There is a linux implementation for
these as well as their native Net+OS.
Jeff.
--
I
