Only public headers (files in a "/include" directory) need the guards.
Private headers (files in a "src/" directory) are only intended to be
included by C files, and don't require them. Not that it hurts to add
guards to the private headers as well.
Chris
On Fri, Sep 09, 2016 at 04:46:44PM
I have some thoughts… (not sure what they are worth)
1) I think having a linker section for retained RAM is a good idea. Another
possible option here is that .bss/.data is retained and heap is not but not
sure if that distinction would be super useful. It would allow skipping of the
startup
- (future) Provide a method to newt by which certain tasks memory can
be linked earlier in RAM, so that for systems where RAM suspension is
desired, a core set of system services can be located there, while
other services can be re-initialized in a second phase.
- This may cause some
PS: if anyone wants to volunteer to do this work, I’m more than happy
to cede responsibility :-)
On 9 Sep 2016, at 10:08, Sterling Hughes wrote:
Hey,
In our coding style we’ve agreed to be C++ friendly:
https://github.com/apache/incubator-mynewt-core/blob/master/CODING_STANDARDS.md
But
