Greg: > Which part of the coding standard
I don't think I did a very good job of explaining the source of the original question. We have absolutely no issue at all with the coding standard. We were just, for lack of a better description, volunteering. We intended to be completely neutral letting the dev team tell us what they wanted as per the quote below. "The FLTK code basically follows the K&R coding style. While many of the developers are not entirely satisfied with this coding style, no one has volunteered to change all of the FLTK source code (currently about 54,000 lines of code!) to a new style." Greg: > I'd be more concerned about the massive code diffs > affecting future merges and diffs for the purpose of > code tracking, and detecting regressions. Perhaps the best approach would be to limit auto formatting to the code we move/write (the fla directory and it's subdirectories) as part of the FLA development process. That should serve to create a bold line between the existing code and the FLA code. The FLA code would be new and thus no backward compatibility would be necessary. Would this address your concerns? I am also working on another post that may make this less of an issue. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
