Hi Jan, > > Any modern compiler (e.g., gcc > 3.4, released 2004) > > supports #pragma once -- and it doesn't pollute the > > namespace with a preprocessor symbol. > > So, get rid of overly verbose include guards. > > Interesting. I wonder why the kernel isn't using it widely yet. I only > find it in one of its tools. Maybe the reason is the limitations of > #pragma once when it comes to identifying the same file included from > different locations (via links etc.).
Yes, exactly, see, e.g., this thread (there are more though): http://lkml.iu.edu/hypermail/linux/kernel/1401.0/02689.html The kernel did not go this route so to have very explicit control over the #include's, something we do not have here. They could've used it in some places but then the idea was dropped for consistency reasons (and the work involved) I guess. > I do not really expect any such complex cases with our simple API > (ebgenv.h), and internal stuff is under our control, so it should be > fine in this specific case. Yes, this was my impression as well. Kind regards, Christian -- Dr. Christian Storm Siemens AG, Technology, T RDA IOT SES-DE Otto-Hahn-Ring 6, 81739 München, Germany -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/20210108195539.2lx4mssqvey3sbqm%40MD1ZFJVC.ad001.siemens.net.
