Click to See Complete Forum and Search --> : Suggestion on Function Handling functions


jimson
07-26-2003, 09:30 AM
i got a suggestion on Function Handling functions
for better standardization and better php

eg.
call_user_func_array() can be changed to func_call_array()
// since user might call internal function, not necessary user functions

call_user_func() can be changed to func_call()
// since user might call internal function also

create_function() can be changed to func_create()

func_get_arg() can be changed to func_arg()
// no need the get word because we can't post or give

func_get_args() can be changed to func_args()
// like the above reason, because we can't post or give
// and we already post/give in call_user_func()

func_num_args() can be changed to func_args_num()
// follow the above standard

function_exists() can be changed to func_exists()

get_defined_functions() can be changed to func_int_list() and func_usr_list()
// since user no need to copy an array or unset to get the user or internal functions list

register_shutdown_function() can be changed to func_reg_shutdown()

register_tick_function() can be changed to func_tick_reg()

unregister_tick_function() can be changed to func_tick_unreg()

jimson
07-27-2003, 08:54 PM
http://bugs.php.net/bug.php?id=24817&edit=2

jimson
07-27-2003, 08:55 PM
somebody please explain this sentence to me?




And lose backwards compatibility? Yeah, right.

epimeth
07-28-2003, 05:33 PM
isn't backword compatibility supposed to mean that old functions work on new versions of the language?

why would implementing new functions lose backwards compatability????


what did you think he meant, tho? I don't see how you're assuming he's an M$ employee?