Sergei,
On 11/04/2021 19:48, Sergei Morozov wrote:
This is great to see this effort happening! As I understand, you also
implement an API for platform-specific parsers but via a much better
extensible API. >
I'm curious if instead of keeping the MySQL syntax in the default parser
and creating one for PostgreSQL, it would make sense to create a MySQL
parser and remove the support for backslash escaping from the default one?
That's a possibility too. I'll think about it.
Perhaps we could work together and come up with an RFC?
Thanks for the offer but I don't think I'll be able to prioritize this
effort over my other projects. Based on the conversation above, reworking
the parser the right way requires a lot of investment and frankly speaking
it's not the most critical problem in the world to solve (all these bugs
are edge cases).
Fair enough. Any other volunteer, I can bribe promising a phpday
elephpant in exchange ;-)
Cheers
--
Matteo Beccati
Development & Consulting - http://www.beccati.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
