I think the uncrustify script is working well. I tested it on the pcbnew/eagle_plugin.cpp which I am going to make a patch for, but it did change a lot, like making multiline comments to have asterisks in each line. So will it be better to submit a patch for the functional changes, such that they are easier to review, or should I make the changes and uncrustify it?
2015-01-06 1:28 GMT+01:00 Adam Wolf <adamw...@feelslikeburning.com>: > I think that is a good idea. > > Is our "coding standard checker" script still working well? > > Adam Wolf > > On Mon, Jan 5, 2015 at 5:23 PM, Nick Østergaard <oe.n...@gmail.com> wrote: >> >> Hi Wayne >> >> I was just looking at the coding style policy in >> Documentation/coding_style_policy.pdf and think the format (pdf) is >> not that great for linking and sharing to newcomers. >> >> Would it be a good idea to convert it to md for the use in the >> doxygen-docs along side the roadmap and stable realease policy? >> >> I would expect that all the formatting in the document can be >> converted to md such that it is "rendered" properly by doxygen. >> >> The bonus is that if you have the doxygen-docs, you will also have the >> coding style policy at hand. >> >> Regards >> Nick Østergaard >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp