+1 to a gradual perltidy. In this case, we should add a comment on processed files like : "#format by perltidy" ie -- Fridolyn SOMERS fridolyn.somers@gmail.com Marsillargues - France <fridolyn.somers@gmail.com> 2012/3/10 Mason James <mtj@kohaaloha.com>
On 2012-03-9, at 10:16 PM, Marcel de Rooy wrote:
+1 for a gradual perl tidy too
+1 to a gradual perltidy from me too
So, best to keep cleaning up incrementally, I think.A As we move from C4 to Koha, that'll be an opportunity to clean up all the modules
-Ian
2012/3/8 Jared Camins-Esakov <jcamins@cpbibliography.com>
+1 to a gradual perltidy
2012/3/8 Fischer, Katrin <Katrin.Fischer@bsz-bw.de>
I agree with Chris C. and Chris N. - I think what we would win does not outweigh the loss of history.
Katrin
2012/3/8 Chris Cormack <chris@bigballofwax.co.nz>
> My counter proposal is tidy as you go. Fix code as you touch it. > > With vim (and other editors) you can easily tidy a block, doing that as > code is changed would be my preference. >
I'd prefer a "pay-as-you-go" approach as well. We could simply
require
all work to be tidied before submitting.
Slow? Yes, but not nearly as messy and preserves the history.
Kind Regards, Chris
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
<fridolyn.somers@gmail.com>