Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Code comments

Code comments

Scheduled Pinned Locked Moved The Lounge
c++questionannouncement
25 Posts 15 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Daniel Turini

    CMM originally was created with an objective in mind: assess if you can give a project to a company and have it done right. After some years, people began using it to run their business, so they can be sure they are "CMM level 5". Let's see two actual samples of CMM in real world: Situation 1: Can you give a complex OS to a small company run by two nerds, running a CMM level 1 (worst level) company, like IBM did with MS ? Surely you won't have the work done. Example 2: If one person alone can code a small although complete UNIX kernel for your embeddedd application, like Linus Torvalds did. So, my conclusion is that by CMM we would never had: DOS, Windows Apple II, Macintosh ICQ Netscape, Internet Explorer CVS and so on... and by CMM all software in the world should be done by IBM. Right ? Crivo Automated Credit Assessment

    N Offline
    N Offline
    Nish Nishant
    wrote on last edited by
    #11

    Very neat way to portray how CMM sucks! Very good!!! :-) Nish p.s. I don't work for a CMM company by the way. Whew!!!

    My miniputt high is now 29 I do not think I can improve on that My temperament won't hold www.busterboy.org

    1 Reply Last reply
    0
    • V Vimal Earnest

      i start with something similar ( our coding standard insists so ) /*******************************.FILE_HEADER.*************** * .File: .xxxxx.c * .Version: .0.0 * .Project Code: .PROJECT * .Author: .Vimal * .Created on: .15 Mar 2002 ************************************************************ * .Summary: * .Note: * * .Revision History: bug fixes and optimizations * ***********************************************************/

      N Offline
      N Offline
      Nish Nishant
      wrote on last edited by
      #12

      I bet you work for a CMM certified company :-) Nish

      My miniputt high is now 29 I do not think I can improve on that My temperament won't hold www.busterboy.org

      V 1 Reply Last reply
      0
      • N Nish Nishant

        I bet you work for a CMM certified company :-) Nish

        My miniputt high is now 29 I do not think I can improve on that My temperament won't hold www.busterboy.org

        V Offline
        V Offline
        Vimal Earnest
        wrote on last edited by
        #13

        Yes I do. Nish, I work at Nest, a CMM level 5 company in trivandrum. :)

        N 1 Reply Last reply
        0
        • V Vimal Earnest

          Yes I do. Nish, I work at Nest, a CMM level 5 company in trivandrum. :)

          N Offline
          N Offline
          Nish Nishant
          wrote on last edited by
          #14

          Vimal Earnest wrote: in trivandrum Wow! A fellow Trivandrumite :-) Cool! Nish

          My miniputt high is now 29 I do not think I can improve on that My temperament won't hold www.busterboy.org

          K 1 Reply Last reply
          0
          • E Emanuele 0

            How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

            D Offline
            D Offline
            David Wulff
            wrote on last edited by
            #15

            I just go in for the simple approach which easily identifies the files as one of ours...

            /*------------------------------------------------------------------*/
            /* Filename: Filename.cpp */
            /* Desc: A quick description of the purpose of this file. */
            /* */
            /* Date: March 2002 */
            /* Author(s): David Wulff */
            /* */
            /* This file is Copyright 2002 Battleaxe Software Limited, and may */
            /* .. not be used or redistributed without license. */
            /* */
            /* License: http://www.battleaxesoftware.com/license/ */
            /*------------------------------------------------------------------*/

            If there are any important revisions made to a file that deserve their own comments, this would be added as a normal comment block underneath the heading or with the appropriate section of code. However (and this one *is* a touchy subject with devlopers), we use comment blocks for each function...

            /*------------------------------------------------------------------*/
            /* processInput */
            /* Process the input events. Called at each frame start. */
            /*------------------------------------------------------------------*/

            We even use these with obvious things like constructors as it makes it easy to tell the tsrta of anew function when you are scrolling quickly through a large file. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …

            1 Reply Last reply
            0
            • E Emanuele 0

              How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

              T Offline
              T Offline
              Todd Smith
              wrote on last edited by
              #16

              I use a VC++ add-in to generate .cpp/.h files. So every file has the same format that looks something like

              #ifndef _REGISTRY_H_
              #define _REGISTRY_H_
              //****************************************************************************
              //**
              //** Registry.h
              //**
              //** Author : Todd Smith
              //** Date : Mon Dec 10 10:21:58 2001
              //** Notes : CMM lvl -1 compliant header
              //**
              //** $Id: Registry.h,v 1.5 2002/01/04 21:20:23 todd Exp $
              //**
              //****************************************************************************
              //============================================================================
              // INTERFACE REQUIRED HEADERS
              //============================================================================

              Todd Smith CPUA 0x007 ... shaken not stirred

              L 1 Reply Last reply
              0
              • E Emanuele 0

                How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

                C Offline
                C Offline
                Chris Hafey
                wrote on last edited by
                #17

                It seems redundant to record the filename, author, date, version and revision history in the file itself when you are using a source control system. We don't have any kind of header on our source code, just #includes. Oh yeah we are ISO-9001 certified. Chris Hafey

                1 Reply Last reply
                0
                • N Nish Nishant

                  Vimal Earnest wrote: in trivandrum Wow! A fellow Trivandrumite :-) Cool! Nish

                  My miniputt high is now 29 I do not think I can improve on that My temperament won't hold www.busterboy.org

                  K Offline
                  K Offline
                  Kannan Kalyanaraman
                  wrote on last edited by
                  #18

                  Nish, I was just about to say, he would be working just a couple of blocks from your work place :-). Cheers Kannan

                  1 Reply Last reply
                  0
                  • E Emanuele 0

                    How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

                    N Offline
                    N Offline
                    Navin
                    wrote on last edited by
                    #19

                    Most our files start out with a header similar to what you have... except it's specially formatted to work with our version control system (PVCS) so that it automatically gets updated with the revision notes we type in. Functions usually have a couple lines explaining what they do (if not trivial), and what the parameters do (if not obvious.) For other blocks of code, I tend to comment WHY this code exists. That seems to be much more useful than just commenting WHAT the code does - that is often self-evident. For instance, you might find a comment like this: // Delete these registry entries becuase the API doesn't do it instead of // Delete HKEY_LOCAL_MACHINE/Software/App/Key :) Winning isn't everything, but then, losing is nothing.

                    1 Reply Last reply
                    0
                    • E Emanuele 0

                      How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

                      R Offline
                      R Offline
                      Rick York
                      wrote on last edited by
                      #20

                      I like Paul DiLascia's header. He often has something like this in it : // If this code works it was written by Paul DiLascia. // If not then I don't know who wrote it.

                      1 Reply Last reply
                      0
                      • E Emanuele 0

                        How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

                        T Offline
                        T Offline
                        Tom Archer
                        wrote on last edited by
                        #21

                        I personally don't believe in comments like this. It's just one more thing to maintain and to quickly become meaningless when just one person in a long chain of developers forgets. To me commenting code like this is a bit like using writeln's to debug - it was useful in its day, but not the best way of doing things now. This sort of information is one of the things that version control software was created for. Cheers, Tom Archer Author, Inside C# Best mini-putt score = 22

                        1 Reply Last reply
                        0
                        • E Emanuele 0

                          How do you begin your code? Do you write comments at the beginning that tell who is the developer, the date, the name of the module?? I usually begin like this: ///////////////////////////// // fileName.cpp //Date: 09/04/2001 // Author: emanuele delbono // Version: 1.0 // Revision history // Date - Author // Comments: ////////////////////// And you?? Do you insert some sort of joke?? :-))

                          T Offline
                          T Offline
                          Tim Smith
                          wrote on last edited by
                          #22

                          Yes, I have stuff like that. But I don't include anything that the source control system automates. Tim Smith I know what you're thinking punk, you're thinking did he spell check this document? Well, to tell you the truth I kinda forgot myself in all this excitement. But being this here's CodeProject, the most powerful forums in the world and would blow your head clean off, you've got to ask yourself one question, Do I feel lucky? Well do ya punk?

                          1 Reply Last reply
                          0
                          • T Todd Smith

                            I use a VC++ add-in to generate .cpp/.h files. So every file has the same format that looks something like

                            #ifndef _REGISTRY_H_
                            #define _REGISTRY_H_
                            //****************************************************************************
                            //**
                            //** Registry.h
                            //**
                            //** Author : Todd Smith
                            //** Date : Mon Dec 10 10:21:58 2001
                            //** Notes : CMM lvl -1 compliant header
                            //**
                            //** $Id: Registry.h,v 1.5 2002/01/04 21:20:23 todd Exp $
                            //**
                            //****************************************************************************
                            //============================================================================
                            // INTERFACE REQUIRED HEADERS
                            //============================================================================

                            Todd Smith CPUA 0x007 ... shaken not stirred

                            L Offline
                            L Offline
                            Lost User
                            wrote on last edited by
                            #23

                            Todd Smith wrote: I use a VC++ add-in to generate .cpp/.h files. Todd, what add-in is this and where can I get it? Michael Martin Australia mjm68@tpg.com.au "Don't belong. Never join. Think for yourself. Peace" - Victor Stone

                            T 1 Reply Last reply
                            0
                            • L Lost User

                              Todd Smith wrote: I use a VC++ add-in to generate .cpp/.h files. Todd, what add-in is this and where can I get it? Michael Martin Australia mjm68@tpg.com.au "Don't belong. Never join. Think for yourself. Peace" - Victor Stone

                              T Offline
                              T Offline
                              Todd Smith
                              wrote on last edited by
                              #24

                              I use a modified version of this generate a .h and .cpp in the project dir (I can send a copy if you like) http://www.codeguru.com/devstudio\_macros/make\_file\_pair.shtml And then a slightly modified version of this to paste blocks of code into a file (one or .h and one for .cpp) http://www.codeguru.com/devstudio\_macros/code\_template\_sandy.shtml Todd Smith CPUA 0x007 ... shaken not stirred

                              L 1 Reply Last reply
                              0
                              • T Todd Smith

                                I use a modified version of this generate a .h and .cpp in the project dir (I can send a copy if you like) http://www.codeguru.com/devstudio\_macros/make\_file\_pair.shtml And then a slightly modified version of this to paste blocks of code into a file (one or .h and one for .cpp) http://www.codeguru.com/devstudio\_macros/code\_template\_sandy.shtml Todd Smith CPUA 0x007 ... shaken not stirred

                                L Offline
                                L Offline
                                Lost User
                                wrote on last edited by
                                #25

                                Todd Smith wrote: I use a modified version of this generate a .h and .cpp in the project dir (I can send a copy if you like) That would be much appreciated Todd. Michael Martin Australia mjm68@tpg.com.au "Don't belong. Never join. Think for yourself. Peace" - Victor Stone

                                1 Reply Last reply
                                0
                                Reply
                                • Reply as topic
                                Log in to reply
                                • Oldest to Newest
                                • Newest to Oldest
                                • Most Votes


                                • Login

                                • Don't have an account? Register

                                • Login or register to search.
                                • First post
                                  Last post
                                0
                                • Categories
                                • Recent
                                • Tags
                                • Popular
                                • World
                                • Users
                                • Groups