Re: [fpc-devel] Unicode in the RTL (my ideas)

2012-08-23 Thread Hans-Peter Diettrich
Daniël Mantione schrieb: * There are no whitespace characters beyond widechar range. This means you can write a routine to split a string into words without bothing about surrogate pairs and remain fully UTF-16 compliant. How is this different for UTF-8? Your answer exactly demonstrates

Re: [fpc-devel] Unicode flame

2012-08-23 Thread Sven Barth
Am 23.08.2012 13:30, schrieb Anton Kavalenka: Dear FPC-all It DOES NOT matter what unicode string (UTF-8 or UTF-16) would be implemented in runtime. Really, does not. Humans are flexible - trust me. Every State proves this everyday. It matters - the compiler have not to be smarter than me. I'd

Re: [fpc-devel] Unicode flame

2012-08-23 Thread Michael Schnell
On 08/23/2012 01:30 PM, Anton Kavalenka wrote: It DOES NOT matter what unicode string (UTF-8 or UTF-16) would be implemented in runtime. OK. Lets do all in in ASM. Here a human can show his skills. -Michael ___ fpc-devel maillist - fpc-devel@lis

[fpc-devel] Unicode flame

2012-08-23 Thread Anton Kavalenka
Dear FPC-all It DOES NOT matter what unicode string (UTF-8 or UTF-16) would be implemented in runtime. Really, does not. Humans are flexible - trust me. Every State proves this everyday. It matters - the compiler have not to be smarter than me. I'd like to DEFINITELY be sure that my string wo

Re: [fpc-devel] MIPS target: progress report?

2012-08-23 Thread Fuxin Zhang
> Does anybody have an update on where the MIPS port has got to after the > flurry of activity in June? Since it cannot catch the time requirement of our project, I have suspended the work temporary due to other affairs. The last time I checked the code(about the end of July) it is able to run the

Re: [fpc-devel] MIPS target: progress report?

2012-08-23 Thread Mark Morgan Lloyd
Pierre Free Pascal wrote: I worked on it quite some time before leaving for holidays, and tried to get it working again with current svn trunk... I haven't yet checked if current svn trunk is usable for mipsel target. Currently, using revision 21906 you should be able to do a complete 'make a

Re: [fpc-devel] Re: Various 2.6.x "fixes" branches?

2012-08-23 Thread Graeme Geldenhuys
On 23 August 2012 08:31, Florian Klämpfl wrote: >> Also, how do I find out in SubVersion at what revision the 2.6.1 branch >> started? > > 2.6.1 did not start yet? I meant the FPC that currently has the 2.6.1 version number... this seems to be the code in the 'fixes_2_6' branch. > It will be b

Re: [fpc-devel] Unicode resource strings

2012-08-23 Thread Sven Barth
Am 22.08.2012 21:45, schrieb Graeme Geldenhuys: On 22 August 2012 10:19, Sven Barth wrote: Depending on how they implement it this might indeed be an interesting feature that we could implement (cherry picking Delphi features ^^). It's already possible, just use IInterface (and TInterfacedOb

Re: [fpc-devel] Unicode in the RTL (my ideas)

2012-08-23 Thread Daniël Mantione
Op Thu, 23 Aug 2012, schreef Hans-Peter Diettrich: Daniël Mantione schrieb: Op Wed, 22 Aug 2012, schreef Felipe Monteiro de Carvalho: On Wed, Aug 22, 2012 at 9:36 PM, Martin Schreiber wrote: I am not talking about Unicode. I am talking about day by day programming of an average programmer

Re: [fpc-devel] Unicode resource strings

2012-08-23 Thread Michael Schnell
On 08/22/2012 07:30 PM, Ivanko B wrote: ... You need to stop your mailer from all the time replying to the wrong message. This makes the forum rather unreadable. -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepasc

Re: [fpc-devel] Using environment-variables in fpc.cfg

2012-08-23 Thread Michael Schnell
On 08/22/2012 08:23 PM, Joost van der Sluis wrote: I thought that it was possible to use environment-variables in fpc.cfg. Sounds like a good idea :-) -Michael ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailm

Re: [fpc-devel] Re: Various 2.6.x "fixes" branches?

2012-08-23 Thread Florian Klämpfl
Am 22.08.2012 21:41, schrieb Graeme Geldenhuys: > Also, how do I find out in SubVersion at what revision the 2.6.1 branch > started? 2.6.1 did not start yet? It will be build from fixes_2_6. According to the TortoiseSVN revision graph, fixes_2_6 has been branched from r18073. > > G. > > > On