M
There's so many functions that'd need cleaning up, yeah, it would break the language. But hey, a new x.0 version would be a good time to say "Yeah, previous versions were crap. Try this one, it's less crappy!" and break some backwards compatibility. There's a lot of legacy cruft they could rid themselves of. And new function names would mean new man pages with new comment sections with hopefully fewer examples of horribly bad coding.More examples of stupid naming is the array handling area. Looking at the docs, it would seem that all array-specific functions are named array_*(), but not so fast, what about sort? arsort? They all deal with arrays, but there's no array_ prefix. Argh... arsort always gets me. Glance at the name quickly and you'd think "Hmm... ARray SORT", but no. it's Array Reverse Sort. So why array_push/pop/shift/unshift? Pop and its cousins by themselves would fit in with some of the other functions' obvious brevity-in-naming.Or usort, uksort? Sorting me and United Kingdom now, are we? If they can have array_uintersect_udiff, usort/uksort should be better renamed to array_sort_callback/array_key_sort_callback. Blah... I'd better get back to work. <30 hours until a hefty project has to be demoed, and many more miles of PHP to scream and kick my way through.