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
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
> >
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, 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/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
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
