Hi, thanks for supporting this! > Maybe just 2 days (of internals and Reddit feedback) is a bit early to > "give up"
I kinda thought so too after I declared defeat, but... The Feature Freeze for 8.2 is July 19! The RFC process requires two weeks each for discussion and voting. If we want to add something good to 8.2, we have to draft the RFC and start discussing it on internals by June 21 at the latest. So I may be a bit impatient, yeah. Other template engines, such as twig or ERB, often have flexible ways of handling whitespace and newline characters around tags. I'm not trying to make PHP more sophisticated to compete with them, but it seemed that just handling trailing newlines would be easy to implement, doesn't complicate the engine, so I proposed this. I am encouraged by the supportive people and will try to work on it again when I have more time to use. Thanks! -- Shinji Igarashi 2022年6月8日(水) 21:48 Guilliam Xavier <guilliam.xav...@gmail.com>: > > Hi, > > > https://github.com/php/php-src/pull/8708 > > > https://www.reddit.com/r/PHP/comments/v5le6h/adding_new_closing_tag_for_keeping_trailing/ > > Thanks for proposing! this "feature" bothered me more than once... > Maybe just 2 days (of internals and Reddit feedback) is a bit early to > "give up" (but I won't blame you either). > > FWIW, the Twig templating engine has distinct delimiters for output > ({{ ... }}) and control ({% ... %}), and the former does *not* eat > newline; for the latter you can use ~%} > (https://twigfiddle.com/54daye), and there are other "whitespace > control" options > (https://twig.symfony.com/doc/3.x/templates.html#whitespace-control). > > For PHP, if we could ignore BC, I would rather have ?> not eat > newline, and add an optional way to do it; but we can't, so I guess > the opposite (e.g. your =?>) is the best we could hope for. > > Regards, > > -- > Guilliam Xavier -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
