Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: coding standards



 On Thu, Jun 5, 2008 at 8:04 AM, Stephen Adler <[hidden email]> wrote: 
> What are common coding standards (or web pages discussing the issue?) 
> 
> I'm working with a group of coders and I need to impose some kind of 
> sensible coding standards... 

One thing that I think would help a lot is if you define your 
standards in terms of options to indent -- that way you can just 
enforce them programmatically -- i.e. before code gets checked in, 
indent is automatically run on the file. At the shop I work in, we 
just use this "pre-check-in checking" to make sure that the copyright 
notices are up to date. 

Also, I don't know if emacs has a similar thing, but I know that 
(g)vim supports having a comment line at the top of a file for 
per-file settings, which could be useful to help make the process 
brainless. 

Gordon 

-- 
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 

_______________________________________________ 
Discuss mailing list 
[hidden email] 
http://lists.blu.org/mailman/listinfo/discuss
 


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org