[Bluemusic-devel] Code Formatting Standards
Brought to you by:
kunstmusik
From: stevenyi <ste...@cs...> - 2004-02-05 23:17:56
|
Hi all, I received my replacement drive yesterday and after a long night am pretty much back up and ready to get going back on blue. =) Today, I've reformatted all of the source code for blue. I was relying on tabs and setting the tabs to be displayed as 4 spaces in my editor(using Eclipse). I've decided that to change now to no longer using tabs and only using spaces, with indentation at 4 spaces. Over time, I've switched from 2 spaces to 4 spaces in the code as my preference has changed. I think with 4 spaces and not relying on editors to display tabs to whatever, this code base will be easier to view by others, as well as myself when not using Eclipse. In regards to brace-style please refer to the existing code. The style I prefer is: if(whatever) { //code } If you're interested in committing any code, please do respect the existing formatting style. I know everyone has their own preference for brace styles and tabbing, but this is the style now set for the project. I'll try to document the coding standards in the developer docs sometime unless someone else wants to add that. =) Thanks everyone! steven p.s. - last I stopped, the cecilia module was coming along nicely. there's some complications with having to create unique variable names in case of multiple types of the same cecilia module are in the same document, but besides that, I think things are going well. it should take me a day or two to get myself reoriented with the code and hopefully will be able to get this out soon. Thanks! |