Hi!
> That's where the compiler warnings/errors come to the game. Except for
> the situations where one does explicit bad casting, which should be
> avoided in the 1st place, if possible.
Could you explain how compiler can handle zpp("s", &char_ptr, &len) with
len being wrong type? If you show me the way for the compiler to warn on
this, you've gone a long way towards convincing me - but so far I've
seen no way to do it. And this is for me one of the major points where
it could break so many things. Any suggestions?
> That being said, I have been advocated warning free php-src for years
> now. I think if we ever start php6 then we should really change our
The problem is nobody wants to work on it. Nobody even cares too much
for keeping unit tests green, which should be way above no warnings in
the priorities ladder. We definitely should do it, but how many people
would sign up for "no warnings" effort as opposed to "new syntax, yay!"
effort? That's like washing dishes instead of playing Minecraft. Don't
get me wrong - I'm all for it and will try to dedicate some of my
copious free time to it (thanks for the reminder, btw). But can we
really pull it off? I hope I'm being too pessimistic here.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227