backwards-compatibility

I'm developing an app that uses android.hardware.Camera.parameters.getSupportedPictureSizes() This is only available from SDK version 8 and I would like to be compatible with SDK 4, so I've done this: if(Build.VERSION.SDK_INT >=8){...} But on the emulator, it seams that it tries to check the reference to this function, and it fails: 02-02 11:20:10.930: ERROR/dalvikvm(1841): Could not find method android.hardware.Camera$Parameters.getSupportedPictureSizes, referenced from method com.test.demo.CameraCustom.takeAPicture Any idea about how to solve this backward compatibility issue? I've tried to

Is Visual Studio 2010 compatible with MVC 1.0 Hello guys, Thanks for reading in advance. I'm working with a MVC 1.0 project and VS2008. I will be very glad to upgrade to VS2010, but I'm doubting about its compatibility with MVC 1.0. Have you done it? How did it result? Visual Studio 2010 will come with ASP.NET MVC 2.0 out of the box, so your best bet is converting your existing 1.0 project to 2.0. Your ASP.NET MVC 1.0 project should be (almost) fully compatible with ASP.NET MVC 2.0 (there are a small number of minor breaking changes). All that is required for converting the project to ASP.NET

I'm starting to learn PHP. I would like to use PHP 5.3 because it's the newest version so far. I'm working on a project in which I'll use PHP 5.2 scripts that someone gave me. Are they going to run just fine even though I'm using PHP 5.3? PHP.net features a guide for upgrading from PHP 5.2.x to PHP 5.3. This includes a section on backwards compatibility . From my experience, the transition from 5.2 to 5.3 went pretty smoothly smoothly. The only problems I had with my app was to ensure my DateTime setting were property configured in my php.ini, and filter out some overly-agressive deprecation

How apps like Hacker News beta have use the Ice Cream Sandwich 4.0 UI on their app and at time work without any problems on 2.3 Gingerbread and 2.2 Froyo? I want to create apps that should work on 4.0 and have backward compatibility like that, but how to do it? GrkEngineer Many apps also use ActionBar Sherlock to support the ActionBar UI. It's built on top of the Support Package that bobygerm mentioned. bobygerm You have to use the Support Package and its support libraries (v4, V7, v13) - Android Developer . Some APIs are not yet included in this support package, it may not cover everything

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . I work on a platform product which requires public compatibility between versions, so some code that was compiled against our previous build should be able to work against our new build without the need to recompile. Is there a tool that would automated this verification, all I could find was How to test binary compatibility automatically? which seems to be for C++ You could try to use the diff

I'm developing a shared library. Let's say I have the following class definition: class MyClass { public: //public interface private: virtual void foo1(int); virtual void foo2(int, bool); virtual void foo3(double); virtual void reserved1(); virtual void reserved2(); virtual void reserved3(); class Impl; Impl* impl_; }; The reserved# virtual methods are not overridden in the client code and not called from anywhere. They serve as placeholders for future expansion. Let's say I replace one of the reserved methods with a virtual function with different signature and implementation: class MyClass {

When will Apple remove the methods/APIs marked as deprecated? After 2 or 3 releases after they were marked, or never? In common usage deprecation merely means that the feature is no longer recommended to be used and MAY be removed entirely in a later release. Wikipedia - Deprecation It is good practice to stop using deprecated features as soon as it is reasonable to as you have no gauruntee how long they will continue to be supported. Sometimes it could be as little as the next release or many dozens of versions later. A quick search for Apple and Deprecation brought up this API reference