On Thu, Mar 18, 2010 at 8:49 PM, HippoMan <hippo.mail...@gmail.com> wrote:
> The reason I'd like this is so I can avoid compile errors if the
> string doesn't exist. This would allow me to do something like the
> following:
>
> String foobar = null;
> try {
> foobar = this.somehowGetStringAnotherWay("foobar");
> }
> catch (SomeSortOfException e) {
> Log.e("MyActivity", "foobar string not found");
> }
>
Let me get this straight - you would rather have a runtime exception that
you just catch and ignore than a compile time error that will quickly
identify your problem and allow you to fix it on the spot?
Why exactly would you prefer this?
-------------------------------------------------------------------------------------------------
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
To unsubscribe from this group, send email to
android-developers+unsubscribegooglegroups.com or reply to this email with the
words "REMOVE ME" as the subject.
