Duncan Gibson wrote: >>> I have the problem that "indent" doubles up the "const" keyword at >>> the end of a function description. Very annoying. So maybe "indent" >>> is not the way to go? Or my particular version is buggy. > > Do you have an example? I haven't noticed this. > >> I didn't try indent, but I experimented with astyle and used >> Ian's proposals, and I also found some *very* strange reformatting >> that wouldn't be acceptable, IMHO. One example (formatted with >> spaces, use fixed font to read): >> >> int *a, // pointer >> b; // var >> char *c; // another pointer >> >> becomes: >> >> int *a, // pointer >> b; // var >> char *c; // another pointer > > I've been idly playing with universalindentgui running uncrustify, > and it does appear that there are options to give: > > int *a, > b; > char *c; > > or > > int *a, > b; > char *c; > > And I'm sure I've seen trailing comments move and align themselves > in the example.cpp, but I can't get them to work with the code above > when added to Fl_Help_View.cxx. But then there many more options than > indent and astyle. The downside is there is no --style-kr to use as > a starting point to adjust to taste. > > I also noticed that astyle's --style=k/r turns off all other options > so you can't start with K&R as base and then tweak it. > > D.
Probably astyle and others that comes with universalindentgui is outdated ! _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
