Danny Kukawka wrote:
> On Saturday 06 August 2005 22:53, Stefan Seyfried wrote:
>>Danny Kukawka wrote:
>>>I wondered also. I would prefer also to know the file. Something like
>>>this:
>>>
>>>syslog(LOG_ERR, "[E] %s:%d: %s", string, __FILE__, __LINE__,
>>>__FUNCTION__, ## args)
>>but this makes the lines even longer, not shorter :-)
>>We could put something like this in a configure --enable-verbose-debug,
>>so we can use it in a experimental build but disable in official releases.
>
> Yes, I know, this makes the lines a littlebit longer, but also more
> informatively. I would replace WARNING, ...,ERROR with [W], ..., [E] and
> remove the '()' anyway. But maybe also the messages self are to long?!
>
> We could maybe add a new debug level for this, but a configure option is also
> o.k. for me.
>
I think we should go with Seife's approach. Finding the file is easy if you know
the function. Emacs, kdevelop and whatever tools find them directly, if you are
working
with vi (cscope probably can jump to functions as well) you have to grep for the
function header, no big deal.
Warning and Error is important I wouldn't short it.
What I was thinking of is a DBG_DBUS Flag, but this is also not very important
and
I can do it if I really have a lot of time (not before 10.0).
Thomas
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel
