backwards-compatibility

what's the difference between -source and -target compatibility?

阅读更多关于 what's the difference between -source and -target compatibility?

问题 When using the Java compiler ( javac ), we can specify two kinds of compatibility. One is using -source and the other is using -target . What is the difference between these two? For example, -source 1.5 and -target 1.6 ? Also, is there any case where we use a different source and target compatibility level? 回答1: From the javac docs: -source Specifies the version of source code accepted. -target Generate class files that target a specified version of the VM. Class files will run on the

Is it okay to use <input type=“tel”/> now?

阅读更多关于 Is it okay to use now?

问题 I'm working on a mobile phone web app and I have several text fields that could benefit from <input type="tel"/> . iPhones will adjust the keyboard for the user, but I'm worried about breaking backwards compatibility. What I'm hoping is that browsers/phone that support this can assist the user and other browser will fall back to a standard text field? Is this an acceptable practice? Does it even work? 回答1: Yes, any unsupported type will revert to the 'type=text' format. I found a good page

Will TortoiseSVN 1.7 work properly against a SVN 1.6 repository?

阅读更多关于 Will TortoiseSVN 1.7 work properly against a SVN 1.6 repository?

问题 I would like to upgrade my TortoiseSVN installation to version 1.7. We have a VisualSVN server running with a SVN 1.6 repository. Do I need to upgrade the repository to 1.7 before I can update my client, or is TortoiseSVN backwards compatible? I know that during the upgrade from TortoiseSVN 1.6 to 1.7, I need to convert my working copy to the new format, but during a commit does it have some logic to see the server version and adapt appropriately? 回答1: In the release notes Older clients and

Which parts of the C++14 Standard Library could be and which parts will be made constexpr?

阅读更多关于 Which parts of the C++14 Standard Library could be and which parts will be made constexpr?

问题 With the new relaxed C++14 constexpr rules, compile-time programming becomes a lot more expressive. I wonder whether the Standard Library will also be upgraded to take advantage. In particular, std::initializer_list , std::pair , std::tuple , std::complex , std::bitset and std::array seem like prime candidates to be marked constexpr wholesale. Questions : which parts of the Standard Library will now be marked constexpr ? which other parts could be marked constexpr ? e.g. why aren't the

Detect IE8 Compatibility Mode [duplicate]

阅读更多关于 Detect IE8 Compatibility Mode [duplicate]

Possible Duplicate: Differentiate IE7 browser and browser in IE7 compatibility mode We have not had time to fully test IE8 with our fairly extensive system. We are also reaching the point at which we can't prohibit the use of IE8. Our users are stubborn and not terribly sophisticated, so we don't feel that we can tell them to use the "Compatibility Mode" button. Instead, we will add the "IE=EmulateIE7" meta tag as a temporary fix. The problem is that when this tag is used, the browser still reports itself to be IE8, which is then detected by our pages and rejected. I can understand why server

g++ always backward-compatible with “older” static libraries?

阅读更多关于 g++ always backward-compatible with “older” static libraries?

问题 I have a few static libraries, which I'm not the owner of, compiled with an old version of g++ 4.3.2 (c++11/c++0x not activated). When I compile my code with g++ 4.6 (no c++11) and link it using g++ 4.6 with these static libraries, it links fine and I do not seem to get any issues at runtime (not tested everything though). I'm tempted to think that forward compatibility is OK. Now I'd like to compile my code with gcc 4.8 with c++11 and still link it with those same, not recompiled static

What modernizer scripts exist for the new ECMAScript 5 functions?

阅读更多关于 What modernizer scripts exist for the new ECMAScript 5 functions?

问题 ECMAScript 5 has quite a few nice additions. John Resig has a good overview here. Here is a good ECMAScript 5 compatibility table. A lot of this stuff can be "faked" for browsers that don't support these functions yet. Do you know of any scripts that can do this? I'm particularly interested in Object.create. For example, Douglas Crockford's JSON script checks if JSON functions exist before creating them. If there was more like the JSON one we could include them when we need to use the new

inflating fragments with compatibility package android

阅读更多关于 inflating fragments with compatibility package android

问题 I am trying to inflate a layout containing a Fragment using the backwards compatibility package. I took the jar file and placed it in the libs folder of my project. I extended Fragment and then tried to inflate it by setting the contentView of the Activity to <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="fill_parent" android:layout_height="fill_parent" android:orientation="vertical"> <fragment class="com.test.fragments.AdFragment" android

How to deal with deprecated classes in Android to keep compatibility

阅读更多关于 How to deal with deprecated classes in Android to keep compatibility

I am getting back to work on an app I worked on a while ago, when I had everything built around Android 2.2 Froyo. I have updated my SDK for the latest APIs and noticed that the ClipboardManager features I was using are deprecated. I updated the code to use the newer ClipData model and tried it out on my Froyo phone and, of course, I get a NoClassDefFoundError in the new code. I've had a look around SO and haven't found any real discussions of general strategy for maintaining backwards compatibility. I'm not entirely sure how I should handle this and other situations where the API differs,

Why is Python 3 not backwards compatible? [closed]

阅读更多关于 Why is Python 3 not backwards compatible? [closed]

I have learned that Python 3 is not backwards compatible. Will it not affect a lot of applications using older versions of Python? How did the developers of Python 3 not think it was absolutely necessary to make it backwards compatible? Is Python 3.0 backward-compatible and why? Python 3.0 implements a lot of very useful features and breaks backward compatibility. It does it on purpose, so the great features can be implemented even despite the fact Python 2.x code may not work correctly under Python 3.x. So, basically, Python 3.0 is not backward-compatible on purpose . Thanks to that, you can