The work arounds get the job done and might be preferable to
isLoggable anyway if the calls to isLoggable are at all expensive.
It is worth understanding how the SDK instrumentation tools work (or
not, in which case maybe isLoggable should be deprecated?).
It seems like a good idea to use androi
Yes I know, I was just trying to show the approach the the Google
platform team (Dianne Hackborn) was taking. If they are unable to
strip debugging then at the moment we have no chance :)
--
RichardC
On Oct 19, 6:38 am, jotobjects wrote:
> That thread was about various ad hoc ways that develop
That thread was about various ad hoc ways that developers are cooking
up to strip logging and that if you do it wrong you will still be
evaluating the logging statements even if they are not output (i.e.,
common sense Java). Apparently developers are working around the
fact that there is no log
See this thread:
http://groups.google.com/group/android-developers/browse_thread/thread/f88b3556d150e1bd/b9747b4cc78565f1#b9747b4cc78565f1
Specifically the responses by Dianne Hackborn
--
RichardC
On Oct 17, 7:50 pm, jotobjects wrote:
> On Oct 17, 7:03 am, Christine wrote:
>
> > On Oct 16, 12
On Oct 17, 7:03 am, Christine wrote:
> On Oct 16, 12:51 am, jotobjects wrote:
>
> > This is still a little unclear to me. AFAIK this is a recommendation
> > to strip out debug logging - logging is not automatically stripped?
>
> Read a message before you reply. Yusuf just said that debug logg
On Sat, Oct 17, 2009 at 7:03 AM, Christine wrote:
>
> On Oct 16, 12:51 am, jotobjects wrote:
>> This is still a little unclear to me. AFAIK this is a recommendation
>> to strip out debug logging - logging is not automatically stripped?
>
> Read a message before you reply. Yusuf just said that d
Logging isn't compiled out automatically in my experience. I can add
verbose and debug level logging statements like these:
Log.v(LOG_TAG, "Verbose test.");
Log.d(LOG_TAG, "Debug test.");
and the output of both show up in "adb logcat" even if I have
debugging off in the application's manifest and
On Oct 16, 12:51 am, jotobjects wrote:
> This is still a little unclear to me. AFAIK this is a recommendation
> to strip out debug logging - logging is not automatically stripped?
Read a message before you reply. Yusuf just said that debug logging is
stripped at compile time.
> Is there a mech
This is still a little unclear to me. AFAIK this is a recommendation
to strip out debug logging - logging is not automatically stripped?
Is there a mechanism for setting the log level as with Log4J and
java.util.logging and commons logging? I haven't been able to get the
Log.isLoggable() method
>From
>http://developer.android.com/reference/android/util/Log.html#d(java.lang.String,%20java.lang.String):
"Verbose should never be compiled into an application except during
development. Debug logs are compiled in but stripped at runtime.
Error, warning and info logs are always kept."
Yusuf
I understand it is meant for filtering out "logcat" messages, but on
what
basis would a developer know when to use which type of API ?
On Oct 15, 2:50 pm, vj wrote:
> What is the significance of having different "priority" levels in the
> Log API ? I am referring to .e(), .d() etc. Also, cons
11 matches
Mail list logo
