On Sat, Apr 9, 2016 at 1:51 PM, Sterling Hughes <[email protected]> wrote:
> Hi Chris, > > On 4/9/16 11:41 AM, Christopher Collins wrote: > >> I know of no other way, aside from using a script to put those guards on >> all the headers. Note however that they only need to go on the public >> include headers (include/), not the private headers in the src >> directories. >> > > Yup, although this should probably just go in the coding > standards/standard header file framework. I don't see there being a reason > to keep these two different, except for a saving a little bit of work now. I'd suggest just going with the guards, as y'all have noted. It's pretty normal boilerplate, so won't scare anybody away. (and as Chris noted: only needed within public headers) >... Cheers, -g
