On Sun, Dec 23, 2012 at 11:12 AM, Leif Ekblad wrote:
> A switch to UTF-8 only affects a
> small amount of the code-base, and doesn't break string references.
>
I do agree with your point of view,
I also see that major Pascal/Delphi frameworks have chosen UTF-8 for string
such as XMLRAD and mORMo
On Monday 24 December 2012 17:45:34 Henry Vermaak wrote:
> On Mon, Dec 24, 2012 at 05:19:58PM +0100, Martin Schreiber wrote:
> > BTW, I actually think about to fork Free Pascal. Not in the near future
> > but the primary goals are defined already:
> >
> > - Back to the roots.
>
> What are the roots
On Mon, Dec 24, 2012 at 05:19:58PM +0100, Martin Schreiber wrote:
> BTW, I actually think about to fork Free Pascal. Not in the near future but
> the primary goals are defined already:
>
> - Back to the roots.
What are the roots?
> - Add the necessary to build the most productive universal prog
On Friday 21 December 2012 18:16:06 Florian Klämpfl wrote:
>
> If nobody is interested in features you need, bad luck for you, you have
> three possibilities: develop them yourself, pay somebody to develop them
> or use another compiler.
BTW, I actually think about to fork Free Pascal. Not in the
On 24/12/2012 13:05, Marco van de Voort wrote:
In our previous episode, Martin said:
Hm that makes it easy to have an incomplete list, that could later
become a problem
half-width spaces etc..., control chars (RTL/LTR...), currently unused
codepoints (that could become anything in future...)
S
Hi,
OK. I'll add needed defines to registry unit for Windows using this
method:
HKEY_LOCAL_MACHINE= windows.HKEY_LOCAL_MACHINE
Yury Sidorov, j...@cp-lab.com
- Original Message -
From: Martin
To: FPC developers' list
Sent: Monday, December 24, 2012 1:13 PM
Subject: [fpc-devel]
Nikolai Zhubr wrote:
Hi Sergei and Mark,
16.12.2012 12:41, Sergei Gorelkin:
[...]
This was caused by insufficient alignment of Double-typed temp
variables, fixed in r23146.
Moreover, it appeared that function UnixToWinAge wasn't doing anything
useful since year 2005, so it was removed in r23145,
In our previous episode, Hans-Peter Diettrich said:
> >> and component libraries to the new strings, RTL and LCL? IMO a typical
> >> loose-loose situation :-(
> >
> > ? No, the old RTL will remain maintained. It's the same codebase, just
> > recompiled.
>
> Sorry, I doubt that it is so easy :-(
On 24/12/12 11:22, Martin wrote:
>
> half-width spaces etc..., control chars (RTL/LTR...), currently unused
> codepoints (that could become anything in future...)
As Marco said, the list will be smaller than the "allowed list".
Also the Unicode specification defines blocks or categories for cod
In our previous episode, Martin said:
>
> Hm that makes it easy to have an incomplete list, that could later
> become a problem
>
> half-width spaces etc..., control chars (RTL/LTR...), currently unused
> codepoints (that could become anything in future...)
Still shorter than what is allowed.
On 24/12/2012 12:17, Marco van de Voort wrote:
In our previous episode, Mark Morgan Lloyd said:
too. So if somebody implements non ASCII identifiers because he needs a
second source Delphi compiler it will be merged because the addition does not
break existing code. I assume utf-8 identifiers wo
In our previous episode, Mark Morgan Lloyd said:
> > too. So if somebody implements non ASCII identifiers because he needs a
> > second source Delphi compiler it will be merged because the addition does
> > not
> > break existing code. I assume utf-8 identifiers would not be very difficult
> >
Writing this from my laptop I do not currently have all the various
checkouts to look at the exact changes myself. But enquiring based on
the reports I have read.
http://bugs.freepascal.org/view.php?id=23523
From FPC trunk r23202 log:
* Include regdef.inc only if XMLREG is defined (non-Wi
Martin Schreiber wrote:
On Monday 24 December 2012 10:23:00 Sven Barth wrote:
As I already wrote there are currently no plans to change that FPC supports
only ASCII identifiers.
I don't think we can trust on that. I hoped that FPC will not use cpstrnew
too. So if somebody implements non ASC
On Sun, 23 Dec 2012, Den wrote:
Hi all,
I must say, it is actually quite fun to be a part of the FPC Developers
mailing list, I don't know why I didn't join sooner. Quite interesting
conversations and ideas, a little bit of bickering but very understanding
people in general, I like it.
On Monday 24 December 2012 10:23:00 Sven Barth wrote:
> Am 24.12.2012 07:48 schrieb "Martin Schreiber" :
> > On Sunday 23 December 2012 17:44:53 Marco van de Voort wrote:
> > > In our previous episode, Michael Van Canneyt said:
> > > > > Do you know how RTTI will be encoded?
> > > >
> > > > I would
Den 24-12-2012 07:53, Martin Schreiber skrev:
On Sunday 23 December 2012 17:44:53 Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Do you know how RTTI will be encoded?
I would guess short/ansistrings, since pascal identifiers must be a
subset of ASCII anyway.
Not
Am 24.12.2012 07:48 schrieb "Martin Schreiber" :
>
> On Sunday 23 December 2012 17:44:53 Marco van de Voort wrote:
> > In our previous episode, Michael Van Canneyt said:
> > > > Do you know how RTTI will be encoded?
> > >
> > > I would guess short/ansistrings, since pascal identifiers must be a
> >
18 matches
Mail list logo
