It would more than likely create some semantic nightmares. I can envision
people doing numpty things like:
array_map('include', $dependencyFilesArr);
While it works, it somewhat obscures what you're trying to accomplish in
the code. The maintainability nightmare alone may be enough to
counterbalance any benefits. Then again, who needs
readability/maintainability when you can write hopelessly impenetrable
code? :)
On Fri, Jul 19, 2013 at 1:23 PM, Arpad Ray <array...@gmail.com> wrote:
> On Fri, Jul 19, 2013 at 5:36 PM, Daniel Lowrey <rdlow...@gmail.com> wrote:
>
>> How deeply ingrained into the engine is this behavior? Is there any chance
>> of language constructs ever passing the tests for callability or is that
>> just a pipe dream that's not worth the implementation effort?
>>
>
> It's actually pretty trivial to provide functions for echo and print (just
> did a 5 minute POC), but I'm not convinced it's very useful. I don't think
> isset would be possible other than making it equivalent to an is_not_null.
>
> If the aim is some sort of consistency, what would you do with constructs
> like define() or include()?
>
> Arpad
>
