[olsr-dev] code style issues

[Hannes Gredler]

hi,

i have noted that there are several different code-styles
  in the repository, which make the tree a bit hard to digest.

  list of clashes (incomplete):

  - mixed (nost notably C++) comment style,
  - different bracing style
  - onliner bracing
  - little/no use of typedefs.

  furthermore many function names have no global unique name.
  e.g. free_everything() - it would make to clean this up first
  b/c if you pull in the olsrd into your distribution 
  all tree indexing tools (etags, opengrok, etc.) are getting
  confused.

what is the right procedure for getting this sorted ?
meybe add a short doc 'olsrd_code_style.txt' and
convert in peacemeal fashion ?

thoughts ?

/hannes