Bug #52424 [Opn->Wfx]: Function naming inconsistency: htmlentities() x html_entity_decode()

Edit report at http://bugs.php.net/bug.php?id=52424&edit=1 ID: 52424 Updated by: rasmus@php.net Reported by: php-bugs at majkl578 dot cz Summary: Function naming inconsistency: htmlentities() x html_entity_decode() -Status: Open +Status: Wont fix Type: Bug Package: Unknown/Other Function PHP Version: 5.3.3 Block user comment: N New Comment: We don't mind change, but our users really really don't like it when we break their working applications for cosmetic reasons. Previous Comments: ------------------------------------------------------------------------ [2010-07-29 02:05:31] php-bugs at majkl578 dot cz Yes and that is what I think should change, because current naming conventions are really horrible. For instance, look at differences between str_replace, strlen, parse_str, htmlspecialchars. All work with same type but their names are completely different. So, string functions should go to String namespace (String\replace()), array functions to Array namespace (Array\search()) and so on. But unfortunately this will not happen because PHP does not like changes... Think about it. ------------------------------------------------------------------------ [2010-07-25 00:19:32] giorgio dot liscio at email dot it php functions uses a lot of different syntax isset is_array isPublic but aliasing is evil and renaming is not appreciated by users... the best thing you can do is implement your renamed function in your namespace bye ------------------------------------------------------------------------ [2010-07-24 07:11:06] php-bugs at majkl578 dot cz Description: ------------ I suggest adding a function htmlentities_decode() as a replacement for html_entity_decode() and possibly deprecate that one. It is really misleading and unintuitive because there are functions htmlspecialchars() and htmlspecialchars_decode() doing similar thing. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=52424&edit=1