[fpc-devel] Alternative parsers

Sven Barth pascaldragon at googlemail.com
Tue Oct 19 10:20:37 CEST 2010


Am 19.10.2010 10:12, schrieb Florian Klaempfl:
> Am 19.10.2010 09:32, schrieb Graeme Geldenhuys:
>> Op 2010-10-19 08:59, Paul Ishenin het geskryf:
>>>
>>> The most wanted feature is "Unicode string support".
>>
>> What Hans-Peter meant is that even if he does implement Unicode String
>> support, that would require changes in the compiler. Florian apparently
>> doesn't like any changes to the compiler,
>
> When did I say this? What I said was: I won't merge changes into trunk
> which implement support for alternative parsers (this is the topic of
> this thread!) because nobody could explain me yet the use of alternative
> parsers for FPC users. So I would spend time in something with no gain
> for users resulting in even less time for other problems. Maybe somebody
> else will merge it, but he takes the burden to fix any regressions and
> maintain the changed code.
>

To be honest (as someone who hasn't yet posted to this topic): You 
sounded very much like "we don't want to merge this" with "we" as in 
"the core devs". It wasn't really clear (at least to me and maybe some 
others as well) that you only spoke for yourself.

And regarding Graeme's comment about Unicode String support: I believe 
that was meant in a sarcastic way.

Regards,
Sven



More information about the fpc-devel mailing list