Don't know about this one though: ./tools/uncrustify1.shWhose file is that?Dunno.Based on 'svn log', it looks like Rick's contribution. I am not a fanof automated cleanup tools (other than sed), so I am unlikely to try it."Machines that can know good style... that'll be the day...."** ;) Cheers, Zach P.S. This is a sentiment that I would love to rue, but I know that the technology is not there yet. If we were, we would not be coding in C. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
That file was actually from Dick. It runs uncrustify with the config file that is also part of the tree. In my experimentation, it looks like uncrustify will handle all pure-syntax style rules assuming someone spends enough time setting the hundreds of options in the config. Dick had made the initial config which does most of the syntax rules.
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
