Philip Sturgeon wrote:
Everything is open for discussion, especially the current error
messages. They are not perfect, so let us know if you have better
ideas.
I'm quite happy to put my hands up and say that despite having been programming since the early 70's some of these 'essential facilities' are simply going over my head. I've programmed with 'strict' languages and had to work around their restrictions in the past, so the 'loose' format of PHP used to be a pleasure. So all of these 'improvements' to keep to nibble away at the that freedom is a pain. My IDE provides all of the 'type-hinting' that I need and a lot more besides, totally outside the final code base. Many of the e_strict rules cause problems resulting in a lot of duplication of code, adding facilities which create more hinting/type checks still seems backwards.
This may just be my misunderstanding the OO basis people are working on, and many of my 'objects' are persisted directly in the database, so the array of elements is simply a record from the database. That record may have a type field so that the resulting array is a mixture of types of object, but all of the same base class. As with other additions made, I don't understand where this 'improved type-hinting' fits into the general development of PHP? How much code will actually benefit from this addition, and how much will simply ignore it?
--
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