Is there some guideline or rationale behind why some WP code functions are prefixed with wp_ ? eg: wp_insert_post() vs. update_post_meta()
|
|
|||||
|
|
This makes not that impressive answer, but - none.
|
|||||||
|
|
Wordpress was and is written by a lot of different people. Patches are discussed inside wordpress trac and whoever submits or assigns to a trac ticket can post patches. If the patch gets accepted and moved into core of an upcoming version it's simply in there. So sometimes functions, vars, etc. gets the prefix while other times they don't. It relies on the participating developers. |
|||
|
|
|
The
|
|||
|
|
|
I always assumed the distinction was that - beyond the basic template tags, which generally just have the simplest descriptive name possible:
I don't know if this was ever intentional, though. And like the other two answers have said, it doesn't hold up consistently. Your example of |
|||||||
|
