Re: [DISCUSS] C++ Header only internal library code

2018-01-08 Thread Udo Kohlmeyer
+1 for consistency On 1/8/18 07:35, Ernest Burghardt wrote: +1 "To be consistent with our Java brothers I would suggest apache::geode::client::internal namespace and headers located in the include/geode/internal directory." On Wed, Dec 27, 2017 at 4:28 PM, Mark Hanson wrote: Sounds good to

Re: [DISCUSS] C++ Header only internal library code

2018-01-08 Thread Ernest Burghardt
+1 "To be consistent with our Java brothers I would suggest apache::geode::client::internal namespace and headers located in the include/geode/internal directory." On Wed, Dec 27, 2017 at 4:28 PM, Mark Hanson wrote: > Sounds good to me. +1 > > Thanks, > Mark > > On Dec 27, 2017, at 9:17 AM, Jaco

Re: [DISCUSS] C++ Header only internal library code

2017-12-27 Thread Mark Hanson
Sounds good to me. +1 Thanks, Mark > On Dec 27, 2017, at 9:17 AM, Jacob Barrett wrote: > > As we move more and more to C++11 the use of templates and header only > implementations balloons. For many of these templates to be useful some > internal utilities must be provided to them but should not

[DISCUSS] C++ Header only internal library code

2017-12-27 Thread Jacob Barrett
As we move more and more to C++11 the use of templates and header only implementations balloons. For many of these templates to be useful some internal utilities must be provided to them but should not be "exposed" as public API themselves. Many large scale projects have similar issues as more and