imacarthur wrote: > > On 7 Mar 2010, at 9:09, Domingo Alvarez Duarte wrote: > > >> Now that you alert me about coding standards I did ask my friend google >> and he told me about this tool: >> http://invisible-island.net/bcpp/bcpp.html > > I'm surprised you did not just use gnu "indent". > It is very powerful, and available by default on most systems. (I > thought you were using gnu tools on your win32 box? If so, you probably > already have gnu indent installed.) > > As far as the coding standard and the CMP, I have to say that I do not > like the format that it mandates much either (in fact I suspect no one > really does) but we have to have something that is an agreed standard, > even if it doesn't really suit anybody... > > So, rather than suggesting tools to retrospectively fix the problem > (which never quite works - in particular these tools often mangle > doxygen comment formatting, which is a Bad Thing) you are best just > writing the patch in the "approved" style. > > Of course, you can develop the patch in any style you like, but then > submit the actual patch in the correct format and all will be well. > > If you submit patches that are inappropriately formatted there is a very > real chance they will be ignored, as no one has the time to fix other > peoples mess, however clever of useful the fix might be! >
I understand your point but I still think that on today's computer power don't use it to do mechanical checks and processes is throw away it's power specially for programmers. Would be nice like you said before (edited): " Of course, you can develop the patch in any style you like, but then submit the actual patch in the correct format through formatter_program_xyz to meet our standards and all will be well. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
