On Sun, 2008-09-07 at 20:32 +0200, Harald Geyer wrote:
[...]
> > What works best for you for small embedded devices while keeping  
> > things very portable and small and readable?
> 
> It might seem strange to mention this on a question about portability,
> but it think the linux kernel coding style has some good points:
> 
> /usr/src/linux/Documentation/CodingStyle

ACK.

[...]
> I think avoiding gnu autotools in v1 was a good idea and should be 
> continued in v2 ... some minor code duplication between supported

It was IMHO never really necessary. And no one did write a patch for it
anyways ....

> systems is ok if it helps speed up things or allows cool features that
> otherwise would be quite complex.
> 
> Fail save but don't annoy: In a mesh it is typically a good idea to
> not start the routing deamon if we fail to load the configuration
> properly. Losing one node doesn't hurt but having one node running
> amok does. OTOH it is annoying if olsrd doesn't come up because it
> doesn't find txtinfo plugin or something similiar - might be that
> you just lost the only route to fix the problem and now need to
> drive through the entire city to get physical access to the node ...

But IMHO you can't get one without the other. OK, one could be more
forgiving with not properly loading plugins.
On the other hand, if the bmf plugin runs amok?

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services




