Boost logo

Boost :

From: Andreas Scherer (as_at_[hidden])
Date: 2000-03-15 02:16:26

beman dawes <bema-_at_[hidden]> wrote:
> What guidelines do you use? How do you deal with the issues you
> raise below? What font? What printing program? What indenting
> style works best? How do other programmers react to your code? What
> happens when you port the code between operating systems? Does code
> that looks good under Windows still look good under Unix or on a Mac?
> Do you have some sample code you could let us see?

Our code layout guidelines are simple: "Keep tabs", "78 character
lines", "Smart auto indent" (in MSVC nomenclature). Using TABs instead
of spaces has proved very useful (the former style*S* of using
different amounts of spaces, ranging from 3, 4, to 6, sometimes all in
a single file, caused more harm).

Personally I use "Comic Sans MS" in the MSVC editor. In the rare cases
that I print my own code, I stick with this. When I print "foreign"
code, I switch to "Lucida Console" (mostly at 8pt, because of line
lengths with 90+ chars). Printing is almost exclusively done (if at
all) from MSVC.

The rest of your questions is quite obscure to me. Do you use a "word
processor" for editing source code? Apart from using "Comic Sans MS" in
MSVC, source files still are plain text, right? I can open any
MSVC-created source file with Vim (on either Win32 or Unix/Linux) and
see it in "Lucida Console" (or whatever fixed font I select for Vim).
As I remarked in an earlier posting, both MSVC and Vim are quite happy
with text files from "the other end", although I sometimes use ":set
ff=unix" (or ":set ff=dos") in Vim.


Boost list run by bdawes at, gregod at, cpdaniel at, john at