On Tue, Jun 16, 2015 at 1:07 PM Brian Geffon wrote:
> I like the idea of CK++, I'd love to see this, my only question is: who is
> officially going to be the maintainer of CK++, will it be the CK community?
> Also, would CK++ require C++11/14 or would it try to be backwards
> compatible with olde
I like the idea of CK++, I'd love to see this, my only question is: who is
officially going to be the maintainer of CK++, will it be the CK community?
Also, would CK++ require C++11/14 or would it try to be backwards
compatible with older versions of C++?
Brian
On Tue, Jun 16, 2015 at 11:57 AM, P
On Tue, Jun 16, 2015 at 12:19 PM Alan Carroll
wrote:
> During the 6.0 bug scrub / planning session there was a lot of discussion
> of Concurrency Kit (libck). The fundamental issue is that CK does not
> compile in a C++ environment and cannot be made to do so without
> significant and incompatib
During the 6.0 bug scrub / planning session there was a lot of discussion of
Concurrency Kit (libck). The fundamental issue is that CK does not compile in a
C++ environment and cannot be made to do so without significant and
incompatible API changes. This is also true for the header files which
