On Wed, May 20, 2015 at 12:01 AM, Vladimir Ozerov voze...@gridgain.com
wrote:
C++11 users can use C++03 projects, but not vice-versa.
Are we sacrificing any features? (sorry, my C++ knowledge is limited).
On Wed, May 20, 2015 at 9:52 AM, Dmitriy Setrakyan dsetrak...@apache.org
wrote:
On
Igniters,
We need to decide which C++ version to use in interop. Currently wide
developer community is in progress of adopting C++11. But if we choose it,
users might have problems if their CPP projects using older C++ revisions
which are still very common.
I think we should stick to C++03
On Tue, May 19, 2015 at 11:27 PM, Vladimir Ozerov voze...@gridgain.com
wrote:
Igniters,
We need to decide which C++ version to use in interop. Currently wide
developer community is in progress of adopting C++11. But if we choose it,
users might have problems if their CPP projects using older
Brane,
Thanks for clarifications, I mistakenly thought that smart pointers were
introduced only in C++11. If they are already in C++03 of course we should
take advantage of them.
On Wed, May 20, 2015 at 12:08 PM, Branko Čibej br...@apache.org wrote:
On 20.05.2015 09:47, Vladimir Ozerov wrote:
On 20.05.2015 09:47, Vladimir Ozerov wrote:
I do not think we will sacrifice anything. C++11 has lots new features such
as smart pointers and lamdas, but I do not see where we can use them on our
public API.
I would definitely recommend using C++03 (or C++98; the only differences
are in the
I do not think we will sacrifice anything. C++11 has lots new features such
as smart pointers and lamdas, but I do not see where we can use them on our
public API.
For example, both Hazelcast and GigaSpaces has the following API for cache
GET:
boost::shared_ptrMyVal val = cacheMyKey, MyVal.get();
