On Wed, Dec 3, 2014 at 11:54 PM, Seth Fowler wrote:
> So I noticed that we don’t say anything about initializer list formatting in
> our coding style guide. I’d like to propose that we standardize this
> formatting:
>
> Foo::Foo(int aBar, char aBaz)
> : mBar(aBar)
> , mBaz(aBaz)
> {
> ….
>
[Sorry, white space got eaten up in the previous mail...]
Nicholas Nethercote wrote:
This is already present in the example at
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes:
class MyClass
: public X // when deriving from more than one class, put each on
Nicholas Nethercote wrote:
This is already present in the example at
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style#Classes:
class MyClass
: public X // when deriving from more than one class, put each on its
own line
, public Y
I have encountered far more examp
+1
On Wed, Dec 3, 2014 at 5:37 PM, Seth Fowler wrote:
> Yes, looks like it is! It’s not explicitly spelled out though - someone
> searching for “initializer list”, say, won’t find it. At a minimum it seems
> worth adding an explicit mention in the text.
>
> - Seth
>
> > On Dec 3, 2014, at 2:03 P
Yes, looks like it is! It’s not explicitly spelled out though - someone
searching for “initializer list”, say, won’t find it. At a minimum it seems
worth adding an explicit mention in the text.
- Seth
> On Dec 3, 2014, at 2:03 PM, Nicholas Nethercote
> wrote:
>
> On Thu, Dec 4, 2014 at 8:54
On Thu, Dec 4, 2014 at 8:54 AM, Seth Fowler wrote:
> So I noticed that we don’t say anything about initializer list formatting in
> our coding style guide. I’d like to propose that we standardize this
> formatting:
>
> Foo::Foo(int aBar, char aBaz)
> : mBar(aBar)
> , mBaz(aBaz)
> {
> ….
>
6 matches
Mail list logo
