FRIENDS, STATIC, GLOBALS

these 3 things i've been told to never use, Globals I can kinda understand, but static and friends...? wtf

note the static is the static keyword

Who has been spreading these vicious lies?

Do not use advices form people who have no idea what they're talking about.

>>4
my comp sci professor....

Friends are stupid. Globals and staticness are not.

>>6
how are friends stupid?

need to rewrite some code? wait no just friend it

>>6
ronry fag detected

will the variable always be passed by reference?
if yes, make it global

else
no

do different instantiations rely on something between them?
if yes make that thing static

are you going to reuse a lot of code that you already made and don't feel like copy pasta...?
Make it a friend and include

friends = one more reason to use mixins (or roles)

CAN SOMEONE TELL ME WHAT'S SO WRONG ABOUT HAVING FRIENDS!!! errr using friends?

less of this

stick to simple c++ please or better still, just use c

more of this

ok, i'll try to make it simple for op

class Dice{
  private:
  int face;
  public:
  Dice(){srand(time(0));rolar();};
  static int FACES=6;
  int obtainFace();
  void roll();
};

int Dice:obtainFace(){return face;}
void Dice::roll(){face=rand()%FACES + 1;}

Every time you create a new Dice you create a new int "face", but you don't create a new int FACES, that's because it's static, it belongs to the class and not to the instance.

ok, i'll try to make it simple for op

class Dice{
  private:
  int face;
  public:
  Dice(){srand(time(0));rolar();};
  static int FACES=6;
  int obtainFace();
  void roll();
};

int Dice:obtainFace(){return face;}
void Dice::roll(){face=rand()%FACES + 1;}

Every time you create a new Dice you create a new int "face", but you don't create a new int FACES, that's because it's static, it belongs to the class and not to the instance.

>>16
>>15
now do friends

>>1
You're professor is telling these lies to you to prevent you newfags fucking up everything right from the start. Until you've learned why those constructions are harmful and what are the exceptions to the rule, obey your professor. Once you've figured shit out, the rule does not apply to you anymore.

>>18
You're professor

>>19
No, I am the professor.

So what's the stats of GOTO these days?

>>21
stats
IHBT

>>21
never use makes program readability horrible

professor 2nd day of class upon asking

>>17
sorry, i forgot. but basically, "friend" allows functions outside the class access it's privates and protected stuff, that's why people bitch about it: example
class CSquare;
 
class CRectangle {
    int width, height;
  public:
    int area (void)
      {return (width * height);}
    void convert (CSquare a);
};
 
class CSquare {
  private:
    int side;
  public:
    void set_side (int a)
      {side=a;}
    friend class CRectangle;
};
 
void CRectangle::convert (CSquare a) {
  width = a.side;
  height = a.side;
}
 
int main () {
  CSquare sqr;
  CRectangle rect;
  sqr.set_side(4);
  rect.convert(sqr);
  cout << rect.area();
  return 0;
}


here, CRectangle can access the "private int side" from CSquare because CRectangle was declared friend of CSquare.
That's the basic notion of "class friendship"

http://www.4shared.com/document/eHwhx78W/Introduction_to_Algorithm.htm

>>24
I see... now why would people bitch about friends?

>>23
This is why no one takes community colleges seriously.

>>27
....state college actually

>>24
That's sort of like a protected class in Java - "public for classfiles in this directory only."

Friends, Romans, countrymen, lend me your ears.

>>30
Yea verily, Anthony. As yet when will ye returns't them ?