2011-10-15 Some time ago, I reformated large amounts of code because its in- dent and layout style was broken and thus lowed maintenance work down. I should have used indent(1) for the rough work. Spending three hours configuring it would have been better than what I did. How- ever, as I haven't had it available I did it how I did it: Used sed and awk for rough processing and afterwards went over every- thing with vi. Without regular expressions it would have taken a week, at least. Now I took a look at indent. It appears to be a half-hearted solution, as it understands some bits of C code, but not every. This means, it will do its job in most cases but will fail on less common ones. It might be worth to build complete C grammar knowledge into such a tool. Maybe the result would be too big, but if indent doesn't know about typedefs, what use are rules that process the standard types only then? Either it can process types or not. Maybe I just get the goal of indent wrong. If it tries to make unformated code at least readable, it surely does it's job. But if it tries to apply a common coding style to some software pro- ject, it fails by being too rough. But I shouldn't complain. Indent is Free Software; a tool someone wrote to solve a problem he had. It likely solved his problem, it might solve someone else's problems as well. If not anyone is free to write a better indent. http://marmaro.de/lue/ markus schnalke