How about introducing a framework level flag, say logLevel / logType, and
framwork users setting this depending upon what should be logged. The
setting for this could be done once and the logger class reading framework
level flag and works accordingly.
Thanks,
Saurabh
On Fri, Jan 20, 2012 at 12:07 PM, Martin Heidegger <m...@leichtgewicht.at>wrote:
> On 20/01/2012 15:29, saurabh jain wrote:
>
>> 1. Have a compiler flag
>>
> Compiler flag works at compile time. This is not acceptable for frameworks
> (as they get deployed with a swc usually). Aside from that logging does
> have (plenty of) usecases after deployment!
>
>
> 2. Implement something like :
>> Log("message", appendAdditionalInformation);
>>
> That was the problem I was talking about: The additional informations
> needed to be passed in by hand. This is not just a lot of work, it is also
> prone to errors and people tend to "forget it".
>
> yours
> Martin.
>
--
Regards,
Saurabh
+91 80991-91166
