I am +1 on using pragma once for ease of use. The change should be one large
PR that changes all the files.
However, there is no performance gain on compilation. Modern compilers are
already optimized for include guards.
-Bryan
> On Jul 31, 2017, at 7:52 AM, Jason Kenny wrote:
>
&g
I am +1 on using pragma once for ease of use. However, there is no performance
gain on compilation. Modern compilers are already optimized for include guards.
-Bryan
> On Jul 31, 2017, at 7:52 AM, Jason Kenny wrote:
>
> I want to bump this again. I started moving to this already
t; > On Jul 31, 2017, at 8:11 AM, Alan Carroll
> wrote:
> >
> > I'll put in for allowing #pragma once. AFAIK it's supported by all the
> compilers we support and is reasonably standard usage. I have read up on
> the problems that can arise and IMHO those are bette
; On Monday, July 31, 2017, 11:17:37 AM CDT, James Peach
> wrote:
>
>
> > On Jul 31, 2017, at 8:11 AM, Alan Carroll
> wrote:
> >
> > I'll put in for allowing #pragma once. AFAIK it's supported by all the
> compilers we support and is reasonably standard usa
complex configure checks... this is a
> supported feature of all compilers that supports C++11.
> Jason
> On Monday, July 31, 2017, 11:17:37 AM CDT, James Peach
> wrote:
>
>
> > On Jul 31, 2017, at 8:11 AM, Alan Carroll
> wrote:
> >
> > I'll put in for al
cement.
> Jason
>
> On Friday, July 7, 2017, 2:07:14 PM CDT, Jason Kenny
> wrote:
>
> Hi all,
> I would suggest we start using
> #pragma once
> instead of the classic header guard of
> #ifndef MYHEADER_H
> #define MYHEADER_H
> ...#endif //MYHEADER_H
>
> On Jul 31, 2017, at 8:11 AM, Alan Carroll
> wrote:
>
> I'll put in for allowing #pragma once. AFAIK it's supported by all the
> compilers we support and is reasonably standard usage. I have read up on the
> problems that can arise and IMHO those are better deal
I'll put in for allowing #pragma once. AFAIK it's supported by all the
compilers we support and is reasonably standard usage. I have read up on the
problems that can arise and IMHO those are better dealt with by cleaning up the
includes and source structure rather than depending on b
suggest we start using
#pragma once
instead of the classic header guard of
#ifndef MYHEADER_H
#define MYHEADER_H
...#endif //MYHEADER_H
The reason for this is that #pragma once:
1) is supported on all the compilers and all the platform combination we use
for quite some time now. 2) it is easier to
+1, Thanks Jason
> On Jul 7, 2017, at 1:07 PM, Jason Kenny wrote:
>
> Hi all,
> I would suggest we start using
> #pragma once
> instead of the classic header guard of
> #ifndef MYHEADER_H
> #define MYHEADER_H
> ...#endif //MYHEADER_H
> The reason for this
Hi all,
I would suggest we start using
#pragma once
instead of the classic header guard of
#ifndef MYHEADER_H
#define MYHEADER_H
...#endif //MYHEADER_H
The reason for this is that #pragma once:
1) is supported on all the compilers and all the platform combination we use
for quite some time now
11 matches
Mail list logo
