On 28/07/2016 10:39, Thomas Bley wrote:
creating an e() function can be a BC break if people already have an e()
function in their code.
The name e is ambiguous to me, is it escape, error, encrypt?
You are free to provide a better rfc, but having e() being optional will also
make security optional.
I wrote an entire e-mail setting out what I think should be the aims of
the feature, and you've picked on a single sentence that said that an
e() function would fulfil *most* of those aims. At no point did I say
"an e() function is the perfect solution". You are attacking a straw man.
I'm not going to get into a back and forth on what "optional" means,
either. I've stated what I think is important, and will leave it there.
Regards,
--
Rowan Collins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
