Issue 768 - Switch from TR1 to C++11

README.md

Index: README.md
diff --git a/README.md b/README.md
index d72ed650ce8cf1465199345bd01d9c752e8a2543..87b71ac8e43011627338c79fbd48afe6ae402a59 100644
--- a/README.md
+++ b/README.md
@@ -51,6 +51,22 @@ Visual Studio and build the solution there. Alternatively you can use the
 `msbuild` command line tool, e.g. run `msbuild /m build\ia32\libadblockplus.sln`
 from the Visual Studio Developer Command Prompt to create a 32 bit debug build.
 
+### Supported compilers
+
+You need a C\+\+11 compatible compiler to build libadblockplus. If you need a C++98 compatible interface or you have a questions about another comiler please [create an

[Wladimir Palant, 2015/08/05 11:19:39]

Nit: Please break that line at 80 characters.

Nit: + has no special meaning in Markdown, no need to escape it.

Typo: "comiler" => "compiler"

[sergei, 2015/08/06 07:35:25]

Thanks.

+issue](https://issues.adblockplus.org/).

[Wladimir Palant, 2015/08/05 11:19:39]

Will we actually create a C++98 compatible interface for somebody who creates an
issue? I don't think so, and IMHO we shouldn't suggest here that we will.

[Felix Dahlke, 2015/08/05 21:28:04]

Fair enough, probably not. I suppose anyone who really wants that is going to
figure out that they can create an issue anyway.

[sergei, 2015/08/06 07:35:25]

Removed mentioning of C++98.

+
+The following C++11 features are currently used:
+* std::shared_ptr
+* std::function

[Wladimir Palant, 2015/08/05 11:19:39]

IMHO, this list is bound to get out of date. Yes, right now we are only using
these two features - because we only had headers for them before. Now people
will start using other C++11 features as well however and they won't think about
updating this list.

Why have it here at all? If this is meant to be normative then it belongs in our
coding style document.

[Felix Dahlke, 2015/08/05 21:28:03]

I was about to object but, rethinking it, I suppose a simple `grep` should
answer this, with no chance of getting out of sync with the code base.
Additionally, if we really do test with the compilers below, it'll be fine
anyway.

[sergei, 2015/08/06 07:35:26]

Agree that there is a big chance to get it out of sync.

+
+The compilation was tested with the following compilers:
+* g++ 4.8
+* Microsoft Visual Studio 2010, 2012
+* clang 3.4 for Android (from android-ndk-r9)
+* clang 3.6 for OS X
+

[Felix Dahlke, 2015/08/05 21:28:03]

Nit: Just one new line between sections, as elsewhere here?

+
 Usage
 -----