TYPO3 Core

To modernise TYPO3 CMS cryptic names should go in favour of speaking names. The cryptic names cObj and cObject are used as variable names all over core and extensions to name different classes of objects.

Rename cObj to contentObjectRenderer, where it addresses a ContentObjectRenderer. Keep the names cObj or cObject, were the names are directly related to TypoScript.

Historically the ContentObjectRenderer and the content objects was all one class. Now theses are separated classes and the separation should be expressed in the naming of variables containing the objects.

As this variable names are used in hundreds of places I think it difficult to improve it in one patch. I suggest as migration path in four steps:

1. Introduce the modern name, while keeping the old name as a valid aliases.

This is easy to do and enables updating the API without pressure of deprecation. Moreover it gives to time to figure out, where to use the new names and where to keep TypoScript related old names.

2. Deprecate the aliases.

Once this has been done and it is clear, what and how to rename deprecate the aliases.

3. Remove the aliases

Consider function names

There are also function names containing the part cObj or cObject. Like with the variables this may either be justified by names of TypoScript or could be improved to a more speaking wording.

I suggest to separate the topic of function names.