Hello All,

I read something recently with regard to the FLTK coding standard. I believe 
there was a comment that indicated the displeasure of many developers with the 
current coding standard. It went on to site the reason for the fact that no 
change had been made due to the lack of a volunteer to make the changes. Since 
the FLA work will ultimately touch, or at the very least, review, each source 
file, we would like to help this along. We propose using one of the many 
available beautifier tools. This would allow the possibility of the tool being 
used to enforce the coding standard. Some form of automation may even be 
possible.

We would like to propose the following:

1. Collect the input of all FLTK developers creating a list of all proposed 
changes.
2. Maintain and publish a tally of all proposed changes.
3. Rinse and repeat until the group agrees.
4. Implement the new standard in the form of a beautifier configuration.
5. Apply the new standard as we work through the code.
6. Update the standard documentation.

Would y'all be willing to work through this with us?

Note: We already make heavy use of a beautifier tool, so we are somewhat 
neutral to the coding standard used. We are simply trying to identify what may 
be a good opportunity to address this, if y'all would like to.


Thanks,
Gerry
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to