> "Controlling the Embedded VM":
>
> http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=d...
Thanks, that was educational, although I couldn't figure out how to
turn it into a solution. ;) I found a few other times this question
has been raised, and it seems like it doesn't have an easy answer.
But ... I noticed that assert statements bloat the .apk, which seems
like a bad thing. So I am now using a pattern of checking a static
final constant: if(ASSERTS) { asserts( someCondition, "Some
explanation" ); }
Setting ASSERTS false strips the related code from the .apk. So far
this is working very well. (I use assertions a lot.)
I am curious: how are all you programmers handling assertions? Do you
use the assert statement, your own concoction, or something else? Are
assertions ill-favored in the Java world or, more specifically, the
phone application world?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
