It looks odd because (afaik) most of these functions were born in Unix and were nice and short. Because of all the abbreviations they're not very suitable for studlycaps.
Unlike the usage of underscores, the usage of studlycaps is totally optional anyway, since function names are case insensitive. Because of this, the usage of studlycaps should be limited to PHP-documentation anyway. So maybe we should remove underscores altogether and leave it to the user if they want to use studlycaps? Just an idea, it's not like there has been a good system in the past. We're trying to improve here. Maybe it's not perfect (yet?), but at least, imho, it's an improvement. - Ron ""Matthew C. Kavanagh"" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > On Fri, 2005-12-02 at 15:09 +0100, Ron Korving wrote: >> strPos() >> arrayMerge() >> isInt() >> imageCreateFromString() > > fEof() or fEOF()? > addCSlashes()? > strIReplace()? > strCSpn()? > stripCSlashes()? > strIPos()? > strIStr()? > strNCaseCmp()? > strNCmp()? > strPBrk()? > strRChr()? > strRIPos()? (That one's my favourite). > strRPos()? > uCFirst()? > uCWords()? > vFPrintF()? > vSPrintF()? > > Looks wonderful. And that's just the strings. ;) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
