So your argument against the One True Indent style is that you use an editor that has a badly programmed print option?
There are a few fixes for this; one trivial one is to run your file through a simple search-replace that finds tabs and replaces them with 2 spaces (if printing in portrait mode, a printer is actually a rather small screen). There are various easy ways to do it; in linux you can script this so you can just type "printSource someFile.java" on the command line, even! - replace the text with sed and send the output to /dev/lp0. Note that the reverse is never possible; you can always convert a file indented with the One True Indent style with a hardcoded tab stop, but you cannot go from an all-spaces indented file to a tab indented file; not all spaces are indents. On Jul 1, 11:48 am, Mark Volkmann <[email protected]> wrote: > I'm surprised that all the replies to this thread are in favor of tabs > over spaces. In my experience, the vast majority of developers favor > spaces. For me there is one main reason I prefer spaces ... printers. > Sometimes I print code. Printers seem to always use eight spaces for > tabs which causes many lines to wrap and makes it harder to read the > code. If there were a universal way to adjust that then I'd be okay > with using tabs for indentation. > > This is the same reason why I don't like when lines are longer than 80 > characters. Many of the lines will wrap when printed. Also, I find it > harder to read code with long lines. That's why newspaper columns > don't extend all the way across wide newspaper pages. > > -- > R. Mark Volkmann > Object Computing, Inc. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
