| News | |
 |
Latest |
|
Archive |
|
Community news |
| Articles | |
|
C++ |
|
Communities and Content |
|
Databases |
|
Editorials |
|
Emacs |
|
General |
|
HTML |
|
Java |
|
Notices |
|
PHP |
|
XML |
| Links | |
|
Apache |
|
C++ |
|
Database |
|
General |
|
HTML |
|
Java |
|
Javascript |
|
Linux |
|
Object oriented programming |
|
Open source |
|
Perl |
|
PHP |
|
Python |
|
Ruby |
|
SOAP |
|
XML |
|
Suggest a link |
| About | |
|
Advertise on zez |
|
Contribute |
|
Contact us |
|
About zez |
C++ Styles |
Categories
C++
Code
Topic:
C++ Styles|
Author: David Masterson |
Time: 12.11.2000 03:44 |
Text:
|
Before you go writing yet another C++ coding style, have you looked at the others that are out there. Place to start is:
http://www.cs.umd.edu/users/cml/cstyle/ In particular, read the Ellemtel style guide. With respect to your Part 1 & 2, here's some questions to consider: * Any recommended directory structure to use in a large project? * Any recommendations on filenames to improve sorting and searching? * Should filenames use underscore or dash or nothing to separate words in the name? * Would you recommend macros for portability issues (ie. #ifdef for system types)? * Should C++ keywords be surrounded by whitespace to prevent confusion with function names (ie. ease grepping)? * What do you think of this style for function definitions? int // returning position in array FindItem( char* string // item to search for ) { ... } * Have you looked at tools for literate programming like the following? http://www.w3.org/Tools/Prog_lang_filters.html Just some things to think about... ;-) |
Message threads
| Topic: | Author: | Time: |
|
|---|---|---|---|
| C++ Styles | David Masterson | 12.11.2000 03:44 | |
| RE: C++ Styles | Gunnstein Lye | 13.11.2000 11:01 |
