[wp-hackers] Deprecated functions in the codex

[Jacob]

I'm seriously feel like documenting the code more. I think that file 
will be the first one I tap. I didn't realize it in the first round, but 
the codex would be seriously useful. I think after the entire source 
code is documented it should obsolete that in the codex and a WordPress 
phpDocumentor site should be set up instead to do the low level 
documentation.

I was actually hoping to steal ("borrow") the theme used on 
wordpress.org for a phpDocumentor layout. It would be damn sexy. Damn 
sexy indeed.

Also, does this mean that any deprecated functions should be moved to 
that file regardless of where it was before?

Robin Adrianse wrote:
> Maybe that should be in the message about it being deprecated, as well?
>
> On Dec 6, 2007 1:20 PM, Kaf Oseo <kaf at szub.net> wrote:
>
>   
>> *sigh*
>>
>> This is exactly what the "Replace With" heading was added for, an
>> example of which is:
>>
>> http://codex.wordpress.org/Template_Tags/the_category_head#Replace_With
>>
>> As Jennifer noted, it would have been nice if these had been marked as
>> "in need of editing." Se la wiki...
>>
>> Over the next day I'll see about making sure all *newer* deprecated
>> functions are so listed with correct replacement info.
>>
>> Cheers,
>> -Kaf
>>
>> Hacker Scot wrote:
>>     
>>> The user experience of landing on a Codex page for a deprecated function
>>> is lousy.
>>>
>>> http://codex.wordpress.org/Template_Tags/get_links
>>>
>>> "This function has been deprecated. That means it has been replaced by a
>>> new function or is no longer supported, and may be removed from future
>>> versions. All code that uses this function should be converted to use
>>> its replacement if one exists."
>>>
>>> OK, so what function should you use instead? No hint whatsoever on that
>>> page. So  you turn to the "Related" section at the bottom of the page
>>> hoping to find a similar function that's not deprecated. But nope - each
>>> of these:
>>>
>>>  get_links_list,  wp_get_links,  get_links,  wp_get_linksbyname,
>>> get_linksbyname
>>>
>>> has the same "I'm stuck in a hole with nowhere to turn" message as
>>> above, no hint as to what to use instead. I think the Codex can do
>>> better. I'd be happy to do some editing in the Codex to fix this, IF I
>>> had a reliable list of all deprecated functions and their replacements.
>>> Is there one?
>>>
>>> ./s
>>>
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>>
>>>       
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>>     
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>   


-- 

Jacob Santos

http://www.santosj.name - blog
http://wordpress.svn.dragonu.net/unittest/ - unofficial WP unit test suite.

Also known as darkdragon and santosj on WP trac.