[fpc-devel] Alternative parsers

[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.

The alternative is: we merge any patch we get and if it's broken, well,
we can hope that somebody provides another patch. But believe me, with
this approach FPC will be unusable within a few months because the
typical patch supplier does not check regression tests but we currently
do it and fix the stuff we took responsibility by merging.