ID: 30063 Comment by: reunion at pacific dot net dot au Reported By: aqsalter at westnet dot com dot au Status: Open Bug Type: Documentation problem PHP Version: Irrelevant New Comment:
aqsalter here: I can't add comments for some reason. What's going on? Previous Comments: ------------------------------------------------------------------------ [2004-09-11 18:35:48] [EMAIL PROTECTED] Add something like See also <function>foo</function>, .... and information about <type>callback</type>. to every function which make use of callbacks. The additional text : "and information ...." could exist as entity, of course ;-) ------------------------------------------------------------------------ [2004-09-11 14:55:26] [EMAIL PROTECTED] Hah, That'll teach me. I ponder, how can we best link that information to pages that use a callback? An entity? Put it in the see-also? Also, aqsalter, I hope this has answered your question. We'll work out how to make the information more accessable so the problem does not recur. Thanks for taking the time to contribute. ------------------------------------------------------------------------ [2004-09-11 13:17:27] [EMAIL PROTECTED] Argh. "something like" ------------------------------------------------------------------------ [2004-09-11 13:16:44] [EMAIL PROTECTED] You mean something http://www.php.net/pseudo-types#language.types.callback ? ------------------------------------------------------------------------ [2004-09-11 11:49:42] [EMAIL PROTECTED] I don't know what is meant by "calling instances", I assume he means "ability to call a method of a class" - This information should be present, but not on this page. I think we need some information about the "callback" type. This information really isn't specific to call_user_func, either. I suggest we pop a language.types.callback page in, and link it somehow from pages that use a callback function. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/30063 -- Edit this bug report at http://bugs.php.net/?id=30063&edit=1
