Re: Using Google styling of #define guards

2019-07-05 Thread Ehsan Akhgari
On Wed, Jul 3, 2019 at 8:45 PM Bryce Seager van Dyk wrote: > On Wednesday, July 3, 2019 at 2:27:30 PM UTC-7, Chris Peterson wrote: > > On 7/3/2019 11:37 AM, Bryce Seager van Dyk wrote: > > > I wanted to clarify, and discuss if needed, our styling of #define > guards. My understanding is that we

Re: Using Google styling of #define guards

2019-07-03 Thread Bryce Seager van Dyk
On Wednesday, July 3, 2019 at 2:27:30 PM UTC-7, Chris Peterson wrote: > On 7/3/2019 11:37 AM, Bryce Seager van Dyk wrote: > > I wanted to clarify, and discuss if needed, our styling of #define guards. > > My understanding is that we are now using Google's style in regards to > > #define guards

Re: Using Google styling of #define guards

2019-07-03 Thread Chris Peterson
On 7/3/2019 11:37 AM, Bryce Seager van Dyk wrote: I wanted to clarify, and discuss if needed, our styling of #define guards. My understanding is that we are now using Google's style in regards to #define guards (https://google.github.io/styleguide/cppguide.html#The__define_Guard). I believe

Using Google styling of #define guards

2019-07-03 Thread Bryce Seager van Dyk
Hi all, I wanted to clarify, and discuss if needed, our styling of #define guards. My understanding is that we are now using Google's style in regards to #define guards (https://google.github.io/styleguide/cppguide.html#The__define_Guard). I believe this would mean for `dom/media/foo/bar.h` I