[
https://issues.apache.org/jira/browse/THRIFT-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161861#comment-14161861
]
Ben Craig commented on THRIFT-2717:
-----------------------------------
Most of the features mentioned in the ticket don't require C\+\+11. Here are
the features that require (or at least sort-of require) C\+\+11.
* unordered map/sets
This could be addressed with boost::unordered instead. Ideally, we make it so
that we can switch to std in an environment
* returning using move semantics, no more ugly 'return via output parameter'
(still possible as option thou - sometimes it's needed for performance)
This can be done with C++98, and with optimizations, it is usually as
efficient. Still, this can be addressed by generating a second interface for
each service that implements the return approach, instead of the out-param
approach.
* enum classes
* initializer lists for constants (maybe)
These would be nice, but I don't know if they justify the confusion, testing,
and maintenance burden of another generator
So -0.9. I really don't like this, but I'm not going to stand in the way if
everyone else wants to go ahead with it.
> C++11 generator
> ---------------
>
> Key: THRIFT-2717
> URL: https://issues.apache.org/jira/browse/THRIFT-2717
> Project: Thrift
> Issue Type: New Feature
> Components: C++ - Compiler
> Reporter: Konrad Grochowski
>
> instead of adding another set of options to 'old' cpp generator I've started
> creating new one in:
> https://github.com/hcorg/thrift/tree/cpp11_generator
> using old as an reference
> main goals:
> * code compatible with old librart (at least for first tests, new lib and
> compiler switches can be added later)
> * no more ugly {{__isset}} structure -> boost::optional for optional values
> * as a result - no more {{__}} in names, which violates C++ standard
> * all generation code will have own unit tests (TDD used wherever possible)
> * generated types headers independent from Thrift header, to allow other
> layers of application using generated types without dependency leaks
> * each type will generate own header/cpp file - easier for user to include
> only used parts.
> * unordered map/sets
> * returning using move semantics, no more ugly 'return via output parameter'
> (still possible as option thou - sometimes it's needed for performance)
> * async client using boost::future
> * enum classes
> * initializer lists for constants (maybe)
> I'm aiming in C++11 subset available in gcc 4.8 and MSVC 2013
> currently I have only complete enum generation, but work is in progress
> all comments etc are very welcome :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
