Re: Language constructs and callability

The danger I see there is the fact that we'd have two different implementations of the same functionality (leading to potential code-rot), and worse, it wouldn't be obvious from userspace when one implementation would be used over the other. (We'd know, but I mean for the average PHP user, leading to weird unreproducible bug reports). -Sara On Fri, Jul 19, 2013 at 9:28 PM, Ryan McCue <lists@rotorised.com> wrote: > Sara Golemon wrote: > > 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. > > That's what I meant by the "backwards compatibility layer". Not saying > we have to deprecate the use as a construct, but why can't we enable the > use as a function (and hence, callback, etc)? It feels less cleaner from > my point of view (userland). > > -- > Ryan McCue > <http://ryanmccue.info/> > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >