[TYPO3-core] RFC: #14339: Better options for deprecation log

Steffen Gebert steffen at steffen-gebert.de
Sun May 9 15:31:07 CEST 2010


Am 09.05.2010, 14:17 Uhr, schrieb Steffen Kamper <info at sk-typo3.de>:

> this is SVN patch request.
>
> Type: Bugfix
>
> Branches: trunk
>
> BT reference: http://bugs.typo3.org/view.php?id=14399
>
> It's really useful for detecting deprecated calls. However the logging
> is imho to static:
> 1) you only can switch it on / off
> 2) if on it writes always to file and to dev log which floods both

> 'log' - write to dev log
Could we call it devlog then?

> @fwrite($file, $date.$msg.LF);
CGL

And what happens, when it's set to TRUE or '1'? I've added a check for  
this. Should we log these values to deprecation log? :D

I also overworked the text for the install tool a bit and fixed the above  
mentioned issues in v2.

Steffen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 14339_v2.diff
Type: text/x-diff
Size: 6107 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100509/82c78d05/attachment.diff>


More information about the TYPO3-team-core mailing list