I was thinking of user code that does e.g.
(Integer)R.string.class.getField("MY_ID_" + i).get().You may not have any, or think you don't, but since there's so little benefit to be had, it seems a good candidate for exclusion. Especially since those names are around elsewhere anyway. On Feb 12, 2:48 pm, Dianne Hackborn <[email protected]> wrote: > On Thu, Feb 11, 2010 at 11:01 AM, Bob Kerns <[email protected]> wrote: > > Yeah, it's a good idea to leave R completely untouched. That includes R > > $string, R$drawable, R$id, etc. etc. There are things look at that > > those via reflection, so the names matter, and there's no significant > > bytecodes to optimize anyway. > > For what it's worth, nothing in the platform cares about the R classes. > Those are only generated for the application's convenience; the platform > doesn't touch them, and will run happily if they even disappear completely. -- 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
