Move inconsistently named class.*.php files

[scribu]

There are several files in wp-includes that have a 'class.' prefix instead of 'class-'.

Some of these are marked as being a part of BackPress, while others aren't (class.wp-xmlrpc-server.php).

I think they should all be consisntly named, regardless if they're included in BackPress or not.

[nacin]

I don't mind the BackPress files being different, but a standard would be nice.

[scribu]

The WP_HTTP_IXR_Client, newly introduced in WP 3.1, for example, is also inconsistently named.

[scribu]

Oups... westi is not a keyword :)

[westi]

Personally I prefer the BackPress way :-)
And we do need a standard.
I'm trying to justify which way is better.

[scribu]

If it improved the file order somehow, I would prefer it too, but it doesn't.

[nacin]

class- is more consistent with nearly every PHP file and PHP file prefix in core, and better because most files are already named that way. We also don't use functions., like BackPress. The more we move, the more annoying a routine svn blame becomes, and update-core $oldfiles grows for basically no good reasoning.

[nacin]

Any more file renames that involve wp-settings.php need to be done by someone who can then deploy the changes manually to wporg, to ensure we don't accidentally take very important bits down on subsequent deploy.

[westi]

Ok.

Don't rename old classes or ones from BackPress that isn't worth the hassle it could cause people.

New classes:

​http://codex.wordpress.org/WordPress_Coding_Standards#Variables.2C_Functions.2C_File_Names.2C_and_Operators

Going to fix the ones I've introduced.

[westi]

(In [16149]) Rename new classes to match our coding standards. Fixes #15280.

[hakre]

I suggest to rename to leftover files which are still not properly named (old, unproperly named files) and place stub-file that do deprecated warnings for the oldy and faulty ones.

That will save backwards compability and us developers the hassle to differ.

Now as we have a standard (or don't we have a standard?).

[nacin]

We have a standard. We've just chosen to leave the BackPress scripts in place.

[hakre]

Replying to nacin:

We have a standard. We've just chosen to leave the BackPress scripts in place.

I'm not a native english speaker, probably you must explain the term "Standard" to me :)

---

Related: #14921

[hakre]

Related: #10287