On 04/01/2010 10:53 AM, ~ TreKing wrote:
On Thu, Apr 1, 2010 at 11:51 AM, Achanta <[email protected]
<mailto:[email protected]>> wrote:
Still looking for someone to confirm it that it does not cause
any problems.
Um ... didn't Michael just do that?
There is no specific problem with what you're doing, except of course
properly testing all supported versions and being careful if / how you
use APIs that did not exist on 1.5.
Here's the question I have: define "be careful". If "be careful" means
inspecting every class/method call you make against SDK level, I think
you're setting yourself up for failure, as it's extremely easy to miss that,
and the only time you find it is at run time, which for a seldom run piece
of code could be pretty elusive.
It's would be a lot better to "be careful" by having some tool -- maybe in
the android dev tool chain or the eclipse plugin -- that "carefully" goes
through your code looking for method/classes that are below the current
SDK level. I'm sure there are even better ways to "be careful".
But as it right now, "be careful" is just a big smelly hack.
Mike
--
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
To unsubscribe, reply using "remove me" as the subject.
