Well, now... to be fair... You could make them functions and use the same parser trick the backtick operator uses. to map the non-parenthesized versions.... feels messy though. I'd just hate to get stuck with a hacky workaround like that for the long term.
On Fri, Jul 19, 2013 at 9:23 PM, Sara Golemon <poll...@php.net> wrote: > Lack of parenthesis and the fact that EVERY project out there takes > advantage of this affordance. So BC *nightmare*. > > > On Fri, Jul 19, 2013 at 9:16 PM, Ryan McCue <li...@rotorised.com> wrote: > >> Johannes Schlüter wrote: >> > So, unfortunately no, language constructs have different semantics which >> > we can't emulate inside function semantics (well ok, it is software, so >> > it is thinkable .. but nobody,yet, came up with a robust patch which >> > doesn't cause maintenance *and* performance penalty) >> >> Is there a reason that echo/print couldn't be implemented as functions >> with some sort of backwards compatibility layer? isset/etc make sense to >> be language constructs, but I can't think of any reason echo/print need >> to be. >> >> -- >> Ryan McCue >> <http://ryanmccue.info/> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> >
