[TYPO3-core] Strategy for deprecation log

Markus Klein klein.t3 at mfc-linz.at
Wed Apr 3 09:42:12 CEST 2013


> Am 02.04.2013 17:21, schrieb Philipp Gampe:
> > Hi Steffen,
> >
> > Steffen Müller wrote:
> >
> >> the result is a huge amount of files without meaningful names. How to
> >> find the needle in haystack, e.g. the related log messages to your
> >> extension?
> >
> > In most installations you should only have 10-30 deprecation messages.
> > You can search the files via grep (or your OS find-in-file tool).
> >
> > IMHO this is an easy fallback mode if no sophisticated solution can be used.
> >
> We may have a show-module in BE, which handles these cryptic filenames.
> I would like to have some more informations with the pure entry:
> last occurence,
> first occurence,
> number of occurences

Just out of curiosity: Why do you need that information?
In my experience, all I ever needed was:
- Which deprecated methods is called
- Where is it called

I'm not interested in the timing. Starting with an empty deprecation log file each entry is "current" and uses deprecated API, hence has to be fixed.

> I think it is a nice attempt as it uses base-technics, which are fast and have
> less potential to failure.
> on each occurence a timestamp may be appended to the file. so this will also
> result in growing files, but not so much than a repetition of the whole
> errormessage.
> bernd
> --

Kind regards

More information about the TYPO3-team-core mailing list