Marcus Boerger wrote:
> 9. __toString) everywhere, but i already said i'll take care of that unless
> i am being held back. So now go for that or live with the fact that php is
> meant to generate html pages which is text output. Thus sooner or later your
> objects create text simplifying that aas much as possible is at least to me
> mor ethan welcome.
Can you clarify that?
> 10. namespace support (we are telling everyone php is ready for the big
> soup. In those scenarios you often find big teams and any help allowing
> things like dedicated responisbilities and preventing communication
> problems is more then welcome.)
-1 before, -1 still.
> 12. {} vs [] cleanup
unicode support already makes such distinction it.
> 12a. using {} for strings could also bring us substr() functionality to {}.
One hand I like it, I think I even proposed things like $str{-1} at one
time, on the other hand it creates a big WTF factor. Overall I'd say, -0.5
> 13. eventually cleanup parameter order. Guys who knows in which functions
> the needle is first or second? My solution is to look up every function
> always which is a bit inefficient. I know the param order in c/C++ and
> sometimes in java but in php storing that info is impossible and useless so
> far.
-1
> 15. i think of splitting dba, making ini-file into dba core and putting all
> but dba core into pecl (further plans for ini-file).
+1 for pecl move, ~0 for the rest.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
