Whoops - sent to MH only - the other list i'm a lot more frequent contributor to always sends stuff to the list regardless of which reply you hit ... Cheers, Wol -----Original Message----- From: Anthony W Youngman Sent: 13 May 2003 11:07 To: 'Mike Hansen' Subject: RE: [Koha-devel] Koha, Style, and Perltidy Paul has said what he - as a major contributor - prefers. What I would suggest is that you enforce all code committed to CVS to be run through whatever the standard "perltidy" is as it's checked in. That way you enforce consistency within the codebase. I don't know if you can make the checkout run through a similar perltidy to convert it to the relevant programmer's preferences? Certainly make sure the FAQ tells them how to make it format to their preferences. Certainly, if you demand that code WILL be run through perltidy, therefore it is a requirement that it is "perltidy friendly", then I don't see that the choice of codebase formatting is of any importance. If a programmer doesn't like the default, he simply has to use perltidy to his preferences on checkin and checkout. Cheers, Wol -----Original Message----- From: Mike Hansen [mailto:mwhansen@hmc.edu] Sent: 13 May 2003 06:58 To: Koha Devel Subject: [Koha-devel] Koha, Style, and Perltidy Hello everyone, It has been suggested a number of times before that we come up with a standard style for Koha scripts in order to make the scripts easier to read. One such way of doing this is using a program called perltidy to go through and format things in a certain style. Perltidy can read its configuration from a seperate file, which would allow us to maintain consistency within the codebase.