Re: Introducing "Array Of" RFC

Hi! > I called your analogy ridiculous because it doesn't take the > comparison seriously. I can write a function which requires 10,000 > parameters, does that mean that we should remove functions from the > language? Come off it. It is all about size of the use case. In my opinion, in language like PHP most of the generics use would be overengineering and overcomplication of things that should be simple - like trying to exactly define the detailed types and subtypes of a deep structure in a wrong point - where the structure already exists and being passed around - instead of ensuring the integrity of the structure when it is being created and updated. Or overspecifying and overdetalizing the types of the elements of the structure in the environment where it produces no benefit (e.g., non-compiled dynamic language environment). I am perfectly aware that there are use cases where it legitimately serves a useful purpose - e.g. huge projects which have rigid coding rules, static typecheck tools and which require it to control complexity which can not be controlled otherwise. I just doubt it is a good use case for PHP. I feel it is just making it - yes, I know it is being said 100 times and not always appropriately, but that's exactly how I feel here - Java with dollar signs and integer-to-string conversions. And I do not accept the argument of "if you don't like it, you don't have to use it". It is true, but only to a point. You can, in theory, use C++ without templates. In practice, if you want to call yourself a C++ programmer, you can not ignore them, not now. Language is also an ecosystem, and I think Java-ifying PHP would take the ecosystem not in the right direction. You, of course, may disagree and thing it is exactly the right direction - there is always a moment where preferences which are subjective come to play and in such a moment there's nothing to do but agree to disagree. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227