On 29.04.2010, at 20:28, Emil Cataranciuc wrote: > Do you guys have some coding conventions for FLTK project? > I am looking at the code and it is all messed up. At least when editing in > vim indentation is bad, but of course that is not the biggest problem.
The coding standards for 1.3 are here: http://www.fltk.org/cmp.php#CODING_STANDARDS Not everyone adheres to them and sometimes, odd tab widths are committed to the SVN - accidentally of course ;-). Some parts of the source were written by outside authors and were never adapted to the coding standard. > If there is, then every time somebody submits a new subversion it must be > checked (the subversion) to follow the rules. > Another choice would be to use a software which would reformat the source > code according to the conventions. At least some of them. Yes, we have been discussing that a few weeks ago. We want to avoid an automated beautifier at this point because it would make it very hard to follow code changes or understand the history of a file. In the next major release though (3.0) we will likely use a tool that applies the coding standards at every SVN commit. > P.S. What shall I know if I want to submit subversions to the project? The best way is to grap existing STR's from fltk.org/str.php, fix them, and attach the changes as a "diff" file to the STR. If you committed a few changes that were useful and good (as decided by the core developers), you can apply (ask Mike) for core developer status. He will then poll among all other developers and you will likely be granted SVN access. - Matthias _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
