From: Kevin R. K. <ke...@kr...> - 2014-01-18 03:01:02
|
George, thanks that is very helpful. On Fri, Jan 17, 2014 at 6:06 PM, George Clark <ge...@fe...> wrote: > Hi Kevin, > > I don't do mh development, but I can share what another project I'm on > did. We faced a lot of angst during the migration to perltidy, and > describe some of the resulting implementation here: > http://foswiki.org/Development/CodingStandards#Formatting_Code and > http://foswiki.org/Development/PerlTidy > > But to summarize briefly, we went with mandatory tidy for the core > project, and "opt-in" for the user contributed extensions. It's controlled > by a "TIDY" file located in the directories. For the project core we went > with the default perltidy settings. No-one can override it. Some > dev's choose to use alternative settings for their contributed extensions, > but those are generally maintained by single developers. > > The one issue we later discovered is that perltidy is version sensitive, > and the defaults change over time. So suddenly after a package upgrade on > our svn server, we were all getting rejected commits due to the files > failing the tidy check. What made it worse was that different > distributions release their versions at different times. Depending upon > the distribution packagers, (.deb, .rpm, .ebuild, BSD Port, etc,) it was > more or less difficult to get everyone on the same release. > > One trick with tidy that is rather well hidden but quite handy is a tag > that will exclude tidy from blocks of code: > > http://perltidy.sourceforge.net/perltidy.html#skipping_selected_sections_of_code > So if you have a block of carefully crafted code for readability, > surround it with #>>> and #<<< comments. > > We still run on a subversion repository with github shadow which makes the > pre/post commit exits pretty easy. Hopefully we will complete the > migration to git. It will be interesting to see how you implement git > controls on this. We have not yet written the tidy hooks for git, or I'd > offer to share. > > George > > > On 01/17/2014 08:11 PM, Kevin Robert Keegan wrote: > > In order to enact the plan to use perl tidy to clean up our coding format, > I need to know what we all think is the "standard" code format. > > To that end, the following survey asks 27 questions about various perl > tidy options. These are by no means all potential options, but I think it > covers the basics. If you have a specific setting that you do not see, > feel free to respond to the mailing list: > > http://kwiksurveys.com/s.asp?sid=4ncamjs0iymia4t267133 > > I reserve the right to interpret the answers in a meaningful fashion. > Some options cannot be used together, and some options used together would > just be silly. > > After this is implemented, we can certainly change individual options if > the result is bad. > > Kevin > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > > > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > > |