php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #24817 Suggestion on Function Handling functions
Submitted: 2003-07-26 07:38 UTC Modified: 2003-07-27 19:08 UTC
From: jimsonchang at yahoo dot com Assigned:
Status: Wont fix Package: Feature/Change Request
PHP Version: 4.3.2 OS: XPbox
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jimsonchang at yahoo dot com
New email:
PHP Version: OS:

 

 [2003-07-26 07:38 UTC] jimsonchang at yahoo dot com 
Description:
------------
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()

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-07-27 13:44 UTC] sniper@php.net 
And lose backwards compatibility? Yeah, right.
 [2003-07-27 19:08 UTC] jimsonchang at yahoo dot com 
ok, i mean maybe can implement double solutions(function's name) in php 4.3.3 and mention to users in "changes list", while in the future version of php maybe > 4.3.4, then only retrench the old functions name.

first,
we wish to make PHP a better programming language
second,
a change is a must.
third,
unless you tell me, u don't really care.
fourth,
if really like that, what da hell u are in php.net?
u work for $M?

there are 2 meanings inside your
[quote]
And lose backwards compatibility? Yeah, right.
[/quote]
i don't want to extend the meaning, but i think i got them.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sun Oct 26 11:00:02 2025 UTC