Date: Fri, 15 Jun 2018 12:21:36 +0000
I don’t expect the outcome to be an enforced standard. So, the current 40% would not have to be changed – they are what they are.
However, I do expect the outcome to be a recommendation that the community aspires to – which means that the 40% will decrease, not because they have been changed but because they are becoming the increasing minority.
-- Gaby
From: tooling-bounces_at_open-std.org <tooling-bounces_at_[hidden]> On Behalf Of David Sankel
Sent: Friday, June 15, 2018 3:58 AM
To: WG21 Tooling Study Group SG15 <tooling_at_[hidden]>
Subject: Re: [Tooling] C++ project layout pool
On Fri, Jun 15, 2018 at 1:28 AM Boris Kolpackov <boris_at_[hidden]<mailto:boris_at_[hidden]>> wrote:
A quick summary of the results: with ~300 answers, ~60% for the split
layout (public headers in include/, sources and private headers in
src/) and ~40% for the combined (everything in a single directory).
Does anyone think that a solution which requires >=40% of C++ codebases to change their directory layouts is likely to achieve consensus?
However, I do expect the outcome to be a recommendation that the community aspires to – which means that the 40% will decrease, not because they have been changed but because they are becoming the increasing minority.
-- Gaby
From: tooling-bounces_at_open-std.org <tooling-bounces_at_[hidden]> On Behalf Of David Sankel
Sent: Friday, June 15, 2018 3:58 AM
To: WG21 Tooling Study Group SG15 <tooling_at_[hidden]>
Subject: Re: [Tooling] C++ project layout pool
On Fri, Jun 15, 2018 at 1:28 AM Boris Kolpackov <boris_at_[hidden]<mailto:boris_at_[hidden]>> wrote:
A quick summary of the results: with ~300 answers, ~60% for the split
layout (public headers in include/, sources and private headers in
src/) and ~40% for the combined (everything in a single directory).
Does anyone think that a solution which requires >=40% of C++ codebases to change their directory layouts is likely to achieve consensus?
Received on 2018-06-15 14:29:10