Alex Aulbach wrote:
PHP made implementation mistakes in the past that led to awkward
>behavior (like objects passed by value in PHP4), but that's never
>stopped things from moving forward and offering up useful features
>that users want. I think putting the technical details aside the
>engine can aid a developer in distinguishing between spotting
>unintended side effects and preventing disastrous consequences.
I like that kind of agile programming, too.
But if someone like me says "come on, lets make it a little bit more
easy, because returning objects from functions is some kind of
unconventional; many developers will make mistakes here..." - why not?
They will. I can tell by sure.
Since I begun reading this mailing list I have the impression, that
there are only PHP-programmers like us out there. But the fact is,
that the most PHP-programmers didn't even read the manuals completly.
You may say "Their fault" "Are they programmers, if they don't?", but
this is first a little bit of ignorance because second this is one of
the best features, that PHP has - this "nicely flow", everybody can do
it. I always think of Bob Ross, when I explain PHP.
The manual that I read bears no resemblance to the current one, and I still have
to find a manual that ACTUALLY explains how I should write code that it 'strict'
compliant. The bulk of the on-line boilerplates are no longer fit for purpose so
how can we expect newcomers to 'get it right first time'
But it's ok, there are no mistakes, there are just happy little accidents.:)
That covers most of my best software :)
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
