Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!decwrl!labrea!rutgers!rochester!pt.cs.cmu.edu!f.gp.cs.cmu.edu!dtw
From: dtw@f.gp.cs.cmu.edu (Duane Williams)
Newsgroups: comp.lang.c++
Subject: Re: Where is "private:" documented?
Message-ID: <2816@pt.cs.cmu.edu>
Date: 28 Aug 88 03:47:48 GMT
References: <COOPER.88Aug26111736@gecrux.steinmetz.ge.com> <8138@alice.UUCP>
Sender: netnews@pt.cs.cmu.edu
Organization: Carnegie-Mellon University, CS/RI
Lines: 23


In <8138@alice.UUCP>, Bjarne Stroustrup, writes:
| ``private:'' was introduced to support people that wanted more
| freedom in laying out their code, especially people who wanted
| the public part to come first. It is a ``cosmetic'' feature.

Even if only "cosmetic," it is a nice feature.  Even though I routinely put
private stuff first, I still write

	class ... {
	private:
		...
	public:
		...
	};

Why?  Because this makes the code much more intelligible, esp. to people who
are not C++ wizards.

Duane
-- 
uucp: ...!seismo!cmucspt!me.ri.cmu.edu!dtw
arpa: dtw@cs.cmu.edu