Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #11975
| From | yatremblay@bel1lin202.(none) (Yannick Tremblay) |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: .h and .cpp |
| Date | 2011-11-30 11:24 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <jb53q3$5om$1@dont-email.me> (permalink) |
| References | <d30834a8-3bf4-49a4-b1eb-b66aef965475@i8g2000vbh.googlegroups.com> <3lk7d7ds9k4h654fveq10cfftbj5pm8nbe@4ax.com> <ad50180d-04cd-4ca6-a24e-b0bbbda72ec7@d17g2000yql.googlegroups.com> |
In article <ad50180d-04cd-4ca6-a24e-b0bbbda72ec7@d17g2000yql.googlegroups.com>, Christopher <cpisz@austin.rr.com> wrote: >> Sounds like a group out-of-control. >> >> Sadly you either have the authority to enforce coding standards, or >> you do not. If you do then "just do it, its the thing to do" OR *its >> your job* is the only reliable answer. Otherwise, live with it chewing >> away as opportunities present themselves, or seek other employment. > >I am beginning to think that might be the case, but if the boss says >"I beleive you, you just have to give some reasoning aside from I said >so." Then I wanted to at least try before joining the "I am looking >for employment" group again. Well, you should be able to justify the rules in your coding guideline. Some of the justification may be weak but they should still be rational. If you can't justify a rule, you may as well remove it and only kep the ones that can be justified. A typical rule is naming convention. Why is it better to use CamelCase rather then under_score_separated_names (or vice-versa). Taken in isolation, neither is better than the other. However, it can be clearly demonstrated that a code base that use either randomly is significantly harder to read than a code base that use a consistent naming convention. Many other rule may appear not useful at first sight but when thinking about long term maintenance, they start becoming useful. Having some classes defined in cpp means that they are potentially harder to find. Keeping files shorter mean that it is easier to track changes and potential side effects, etc.
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
.h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-28 09:20 -0800
Re: .h and .cpp Leigh Johnston <leigh@i42.co.uk> - 2011-11-28 17:30 +0000
Re: .h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-28 10:39 -0800
Re: .h and .cpp Tobias Müller <troplin@bluewin.ch> - 2011-11-28 19:09 +0000
Re: .h and .cpp ralph <nt_consulting64@yahoo.net> - 2011-11-28 12:37 -0600
Re: .h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-28 10:48 -0800
Re: .h and .cpp ralph <nt_consulting64@yahoo.net> - 2011-11-28 14:24 -0600
Re: .h and .cpp yatremblay@bel1lin202.(none) (Yannick Tremblay) - 2011-11-30 11:24 +0000
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-12-01 21:42 +0000
Re: .h and .cpp Rui Maciel <rui.maciel@gmail.com> - 2011-12-02 02:03 +0000
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-12-02 20:59 +0000
Re: .h and .cpp "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2011-11-28 19:45 +0100
Re: .h and .cpp Leigh Johnston <leigh@i42.co.uk> - 2011-11-28 19:03 +0000
Re: .h and .cpp "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2011-11-28 20:36 +0100
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-28 22:52 +0000
Re: .h and .cpp yatremblay@bel1lin202.(none) (Yannick Tremblay) - 2011-11-30 11:39 +0000
Re: .h and .cpp Juha Nieminen <nospam@thanks.invalid> - 2011-11-30 12:50 +0000
Re: .h and .cpp yatremblay@bel1lin202.(none) (Yannick Tremblay) - 2011-11-30 13:57 +0000
Re: .h and .cpp Juha Nieminen <nospam@thanks.invalid> - 2011-11-30 15:06 +0000
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-30 16:21 +0000
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-30 16:12 +0000
Re: .h and .cpp Goran <goran.pusic@gmail.com> - 2011-11-28 10:58 -0800
Re: .h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-28 13:30 -0800
Re: .h and .cpp Tobias Müller <troplin@bluewin.ch> - 2011-11-29 06:44 +0000
Re: .h and .cpp Goran <goran.pusic@gmail.com> - 2011-11-29 01:17 -0800
Re: .h and .cpp Nick Keighley <nick_keighley_nospam@hotmail.com> - 2011-11-30 00:53 -0800
Re: .h and .cpp "Alf P. Steinbach" <alf.p.steinbach+usenet@gmail.com> - 2011-11-29 10:57 +0100
Re: .h and .cpp yatremblay@bel1lin202.(none) (Yannick Tremblay) - 2011-11-30 12:05 +0000
Re: .h and .cpp Rui Maciel <rui.maciel@gmail.com> - 2011-11-28 20:07 +0000
Re: .h and .cpp Geoff <geoff@invalid.invalid> - 2011-11-28 12:17 -0800
Re: .h and .cpp Ian Collins <ian-news@hotmail.com> - 2011-11-29 11:41 +1300
Re: .h and .cpp gwowen <gwowen@gmail.com> - 2011-11-29 07:37 -0800
Re: .h and .cpp Goran <goran.pusic@gmail.com> - 2011-11-29 00:08 -0800
Re: .h and .cpp Daniel <danielaparker@gmail.com> - 2011-11-29 08:31 -0800
Re: .h and .cpp ralph <nt_consulting64@yahoo.net> - 2011-11-29 14:49 -0600
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-30 00:21 +0000
Re: .h and .cpp Andy Champ <no.way@nospam.invalid> - 2011-11-28 21:30 +0000
Re: .h and .cpp Paavo Helde <myfirstname@osa.pri.ee> - 2011-11-28 18:05 -0600
Re: .h and .cpp Paavo Helde <myfirstname@osa.pri.ee> - 2011-11-28 18:27 -0600
Re: .h and .cpp Juha Nieminen <nospam@thanks.invalid> - 2011-11-29 07:55 +0000
Re: .h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-29 12:15 -0800
Re: .h and .cpp Leigh Johnston <leigh@i42.co.uk> - 2011-11-29 20:19 +0000
Re: .h and .cpp Christopher <cpisz@austin.rr.com> - 2011-11-29 12:31 -0800
Re: .h and .cpp Jorgen Grahn <grahn+nntp@snipabacken.se> - 2011-11-30 00:31 +0000
Re: .h and .cpp Juha Nieminen <nospam@thanks.invalid> - 2011-11-30 09:43 +0000
Re: .h and .cpp Ian Collins <ian-news@hotmail.com> - 2011-11-30 09:23 +1300
csiph-web