johnsonm at gmail.com
Thu Jun 14 13:38:31 EDT 2007
The nice thing about Perl Tidy is that everybody can have their
own config file. There could be a bioperl default config that gets
applied at checkin time. Anybody that didn't like it could script
checkouts to get run through their own config. Diffs might get a
little hairy, but as long as you tidy before diffing, it shouldn't be
too bad. Speaking of which....coding style is controversial enough,
but since that's already been opened, what about CVS vs Subversion? 8)
Some of the scripting for this sort of thing might be easer in
Subversion. Though maybe something like Git would fit the developer
model better (more support for distributed development).
On 6/14/07, Sendu Bala <bix at sendu.me.uk> wrote:
> Nathan S. Haigh wrote:
> > I'm just wondering if anyone passes their modules through perltidy in
> > order for them to have the same look/feel? If so, do you have a
> > .perltidyrc file? Also, is it worth running the Bioperl modules through it?
> I don't use it, but I was contemplating the same thing. Chris uses it
> from time to time and I think we have a similar taste in style.
> But we'd have to hammer something out that was agreeable to everyone.
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
More information about the Bioperl-l