ID:181489
 
The new API for the Android v2.2 features a new application failure call.

Presenting!

android.util.Log.wtf()

What a Terrible Failure: to report a condition that should never happen!
Oh man, I usually do stuff like this when I code in DM while testing. I usually type
world<<"wtf"


Of course it's only for finding problems along the line of code, and it is removed later on o:
They are geniuses!
In response to Leur
Leur wrote:
Oh man, I usually do stuff like this when I code in DM while testing. I usually type
world<<"wtf"

Of course it's only for finding problems along the line of code, and it is removed later on o:
They are geniuses!

i do the same thig :D, i AGREE
In response to Leur
Leur wrote:
Oh man, I usually do stuff like this when I code in DM while testing. I usually type
world<<"wtf"

Of course it's only for finding problems along the line of code, and it is removed later on o:
They are geniuses!

I use numbers.
//do stuff
world << 1
// do more stuff
world << 2
// do more stuff
world << 3
// etc


I find it to be more useful than random text strings. <.<
In response to Tiberath
I use strings also:
world << Yes, this piece of code works!

world << this one too..

world << the code doesnt work, booo
In response to Tiberath
Tiberath wrote:
Leur wrote:
Oh man, I usually do stuff like this when I code in DM while testing. I usually type
world<<"wtf"

Of course it's only for finding problems along the line of code, and it is removed later on o:
They are geniuses!

I use numbers.
//do stuff
> world << 1
> // do more stuff
> world << 2
> // do more stuff
> world << 3
> // etc

I find it to be more useful than random text strings. <.<

I use numbers too often; recently I've likened to making a debug function and giving some specifics like proc name, and a number.
Too bad there isn't an actual way to get the proc name when debugging, like ___PROC___..
I think every API needs a wtf function; I'm going to add it as a feature request.