Thread: Struct variables initialised?

Or you may see this using the initilization list. Doing it in the body is assignment. Data members are initilized prior to the ctor's body; although not true for built in types as there is no guarantee it was initilized to anything. For non built in types the default ctor is called first if you do not do it yourself in the initilization list, then assignment occurs in the body.

Code:

class SearchArea
    {
      public:
             int Fscore;                               //total value to asses select node or not
             int Gscore;                         //movement cost
             int Hscore;                                //heurestic             
             int Walkstate;                           //is it valid terrain
             int Liststate;                           //is it available? on open or closed list             
             int STnode;                               //is it a / the search start point 
             int TGnode;                              //is it a / the search target point             
             int Xcord;                                 // map node X (across) location
             int Ycord;                                  // map node Y (down) location
             SearchArea() : Fscore(0), GScore(0)....etc
             {  }
      };

@C_ntua: every time I see text highlighted red I hover over it to see if it's a link or not. Which is why I prefer to highlight in blue.

I suppose I should mention that if you're creating a class out of this, at least consider not making all of the member variables public; i.e., use encapsulation (for the record, that is in fact a link).

Originally Posted by whiteflags

You can't really use constructors with arrays anyway. I don't really see a problem with what you have, besides how it looks like you could use some bool variables. Is something confusing you?

Since someone already pointed out my obvious blunder today, I'm going to point out that you absolutely can use a constructor with an array. It's called the default constructor; the one that takes no arguments!

Originally Posted by whiteflags

I knew that, but it's just such a painful and stupid restriction.

Why is it stupid? Even if the language supported it, you'd be restricted to a single argument list, and all the objects would be initialized identically.

In my experience, objects that do not have default constructors are not the sort of objects you would have in an array in the first place.

This... >>>

Code:

   class SearchArea
    {
      public:
             int Fscore;         // total value to asses select node or not
             int Gscore;         // movement cost
             int Hscore;         // heurestic
             int Walkstate;      // is it valid terrain
             int Liststate;      // is it available? on open or closed list
             bool Nodestate;     // is it available for use?
             bool STnode;        // is it a / the search start point
             bool TGnode;        // is it a / the search target point
             int Xcord;          // map node X (across) location
             int Ycord;          // map node Y (down) location
             int ParentPOS;      // point to parent node

             SearchArea()
             {
              Fscore = 0;
              Gscore = 20;
              Hscore = 0;
              Walkstate = 1;
              Liststate = 2;     //Neutral until node is accessed then 0 or 1
              Nodestate = true;
              STnode = false;
              TGnode = false;
              Xcord = 0;
              Ycord = 0;
              ParentPOS = 0;
             }

      };

means i can get rid of this ! >>

Code:

for(dwn = 0; dwn < dwnMax; dwn++)
   {
           for(acr = 0; acr < acrMax; acr++)
           {
               mapnode[dwn][acr].Xcord = acr;
               mapnode[dwn][acr].Ycord = dwn;
               mapnode[dwn][acr].Walkstate = 1;
               mapnode[dwn][acr].Nodestate = true;
               mapnode[dwn][acr].STnode = false;
               mapnode[dwn][acr].TGnode = false;
              // next membervar
              // next membervar
              // blah
              // blah blah
              // ad nauseum..
            }
   }

Magic, i love it! thanks for the advice. i think maybe all the members should be private really.