[Typo3-dev] using devLog instead of debug in the core?

[Ries van Twisk]

René Fritz wrote:

>>>But I strongly sugest to use a common one-line format. Like
>>>
>>>if ($this->writeDevLog) ...
>>>      
>>>
>>Good, but what to do about the static methods of eg t3lib_div?
>>
>>/* WRITE DEV LOG */ t3lib_div::devLog(..)
>>    
>>
>
>We should agree on a common format but in fact it doesn't matter if devLog 
>calls are one liner and just every line with "t3lib_div::devLog" in it will 
>be deleted by the "tuning" script.
>
>But we have to put a if() in the beginning of the line. 
>
>if (TYPO3_DLOG OR $TYPO3_CONF_VARS['SC_OPTIONS']['t3lib/class.t3lib_div.php']
>['writeDevLog'])  t3lib_div::devLog(...
>
>This is ugly isn't it?
>
>
>René
>
>  
>
This is what I currently use:

            if ($this->writeDevLog)    
t3lib_div::devLog(basename(__file__).':'.__LINE__.'|'.sprintf('Form (%s) 
not found in template ',$NameOfForm), $this->extKey, 3);

I also noticed that the cc_devlog does not hold many options to filter 
any of the data in the BE,
is there any plans to change this? Otherwise I would love to create some 
extra options in it.
This is what I have in mind:

1) Make a filter so it only shows the devLog of one extention
2) Make a delete option so it only delete from one extention, and not 
the complete log.

cheers,
Ries