Hello Antony,
do not start the arguments again - read the archieves instead. We agreed
that type hints do not accept null and that only in case we allow = null we
allow typehinted values also to accept null. Since there was a good reason
to allow =null we just went this way. And plieeeze, we are not java and
don't have java's need for allowing null in any parameter. In php that
would just be stupid (imo).
marcus
Saturday, November 19, 2005, 12:08:36 PM, you wrote:
> On 19.11.2005 10:21, Stanislav Malyshev wrote:
>> SM>>Yes, I think too that compiler can catch this and output an error. Though
>>
>> On the second thought - if we don't write a default, is null allowed to
>> places typehinted as array? If not, we should keep both things consistent.
>> I.e., if we allow it as default, we should allow it in typehint too. This,
>> however, may lead to some surprises. I know Java allows nulls to represent
>> any type - should we do the same?
> I think yes, NULL should be able to represent "nothing of any type".
> That makes it consistent and that's what I would expect.
> --
> Wbr,
> Antony Dovgal
Best regards,
Marcus