Hi Kalle, > >> +#ifndef __BLUETOOTH_H > >> +#define __BLUETOOTH_H > > > > No ifdef guards please. > > I'm curious, why not?
the ifdef guards are only needed for public exposed include files to protect against circular inclusion. For local headers I do want it fail if anybody attempts a circular inclusion. If they are needed, then it is a good sign that something is way too complex. Regards Marcel _______________________________________________ ofono mailing list [email protected] http://lists.ofono.org/listinfo/ofono
