I would appreciate that, though I think I have a bug in the version of my Eclipse in which tabs aren't converted to white spaces correctly. I think I need to do an update as it's an early version of 3.4.
As for line length, I'm used to using 80 but only for historical reasons. If we have an exported formatter profile then that doesn't matter as Ctrl-Shift-F will sort that out automatically. :) Cheers, Chris 2009/5/26 Todd Volkert <[email protected]> > >>On the Coding standard, what do you think on export your Eclipse > >>settings and post the file in Subversion (in trunk root, or in tools, > >>or in an eclipse-specific folder, or other ...) ? > >>So others could simply import it, and if/when needed reformat sources. > > > > This is a good idea. We actually have a TODO to write up an official > coding standards doc. Just haven't had time to do it yet. > > Actually, Eclipse has the ability to export a code formatter profile. > (Window->Preferences->Java->Code Style->Formatter->Edit->Export). I > use Emacs, but Greg, since you use Eclipse, you could export the code > formatter you've been using and check it into SVN for the benefit of > others. Then, we can make updates to it as needed and always keep the > up-to-date code style in SVN. Thoughts? I don't know what you've > been using as your maximum line width in your formatter, but I vote > for 120 characters. > > -T >
