Re: [Flightgear-devel] Coding Style (Discussion Proposal)

2007-07-03 Thread Pigeon
> Variables > - > The names of private attributes of a class begin with an underscore followed > by a lowercase letter, i.e. _pitch, _altitude Seems to be a widely used convention, however according to the "handbook" they should be avoided. Things starting with _ (and __) are res

Re: [Flightgear-devel] Coding Style (Discussion Proposal)

2007-07-03 Thread Thomas Förster
Am Dienstag 03 Juli 2007 13:54 schrieb Thomas Förster (actually it was Tim Moore :-) ): > I personally hate underscores or any other indication that a variable is > a private member, with the rationale that a cursory reading of a > well-written class will quickly give you that information anyway,

Re: [Flightgear-devel] Coding Style (Discussion Proposal)

2007-07-03 Thread Thomas Förster
Repost of (relevant parts) of Tim Moore's original posting in another thread to keep things organized :-) With permission Please use this thread for coding style discussions. Thomas > File Naming > - > All filenames are all lower case. Header files end with the suffix .hxx,

Re: [Flightgear-devel] Coding Style (Discussion Proposal) (was crash in AI traffic)

2007-07-03 Thread Tim Moore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Förster wrote: > Am Dienstag 03 Juli 2007 10:31 schrieb Martin Spott: >>> Perhaps you recall this thread: "C++ code beautifier / >>> Codingstandardsproposal" >>> >>> Seems to me that we are just revisiting these issues. >> I can't remember havin

[Flightgear-devel] Coding Style (Discussion Proposal)

2007-06-12 Thread Thomas Förster
Hi all, since I don't like spending a sunny weekend in fruitless hidden discussions about "refactoring is bad if it reformats code" I've put up some thoughts about a possible style guide for Flightgear: CODING POLICY: == File Naming - All filenames are all lower cas