function prefixes... are they needed?

[mscava]

Recently I've came to a small problem... I've read few coding
guidelines, to improve and standardize my style. Most of them advised
me to use function prefixes such as Get, Set, Compute etc..

I understand that avoiding Set prefix might be very confusing and I
feel that one is right.

But what about others?

class Rectangle
{
public:

inline int ComputeArea() const { return w_ * h_; }

inline int GetX() const { return x_; }
inline int GetY() const { return y_; }

inline int GetWidth() const { return w_; }
inline int GetHeight() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

I feel like it's just too verbose... what about:

class Rectangle
{
public:

inline int Area() const { return w_ * h_; }

inline int X() const { return x_; }
inline int Y() const { return y_; }

inline int Width() const { return w_; }
inline int Height() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

Can anyone advise me one of these? Or at least show me some pros &
cons?

Thanks

[Alf P. Steinbach]

* ms****@gmail.com:

Recently I've came to a small problem... I've read few coding
guidelines, to improve and standardize my style. Most of them advised
me to use function prefixes such as Get, Set, Compute etc..

I understand that avoiding Set prefix might be very confusing and I
feel that one is right.

But what about others?

class Rectangle
{
public:

inline int ComputeArea() const { return w_ * h_; }

inline int GetX() const { return x_; }
inline int GetY() const { return y_; }

inline int GetWidth() const { return w_; }
inline int GetHeight() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

I feel like it's just too verbose... what about:

class Rectangle
{
public:

inline int Area() const { return w_ * h_; }

inline int X() const { return x_; }
inline int Y() const { return y_; }

inline int Width() const { return w_; }
inline int Height() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

Can anyone advise me one of these? Or at least show me some pros &
cons?

The first is Java, the latter starts to look like C++. The word
"inline" is superflous and should be removed. Otherwise style is
subjective, so even though I have other preferences, if you like the
second example's style, go for it.
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[Jim Langston]

<ms****@gmail.comwrote in message
news:11*********************@y80g2000hsf.googlegro ups.com...

Recently I've came to a small problem... I've read few coding
guidelines, to improve and standardize my style. Most of them advised
me to use function prefixes such as Get, Set, Compute etc..

I understand that avoiding Set prefix might be very confusing and I
feel that one is right.

But what about others?

class Rectangle
{
public:

inline int ComputeArea() const { return w_ * h_; }

inline int GetX() const { return x_; }
inline int GetY() const { return y_; }

inline int GetWidth() const { return w_; }
inline int GetHeight() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

I feel like it's just too verbose... what about:

class Rectangle
{
public:

inline int Area() const { return w_ * h_; }

inline int X() const { return x_; }
inline int Y() const { return y_; }

inline int Width() const { return w_; }
inline int Height() const { return h_; }

private:

int x_, y_;
int w_, h_;
};

Can anyone advise me one of these? Or at least show me some pros &
cons?

I used to use SetX and GetX, but after a conversation here on the newsgroup
about if I'm using setters and getters, why not just make it public, etc...
I decided that it made more sense not to use them.

I use youre second method, although without inline.