the position of the static keyword in member method declaration

Question

Is there any difference between

class C { static int func(); };

and

class C { int static func(); };

I'm trying to remove the keyword static in someone else's code base. And I want to make sure I understand what the second example means before I do that.

[Edit] The reason to remove static: C was a "class" with no member variables and full of static methods. I think it's more proper to make "C" a namespace with normal functions instead of a class.

Because C was a "class" with no member variables and full of static methods. I think it's more proper to make "C" a namespace instead of a class. Am I right? — GuLearn
– GuLearn, Commented Apr 19, 2013 at 14:26
That's indeed the idiomatic C++ approach. The original coder might have been a Java developer (they don't have namespace). — MSalters
– MSalters, Commented Apr 19, 2013 at 14:32
@user2207811: You can find people that will fall both ways. Using a class forces qualification of the functions that are called, and avoids potential conflicts with unqualified functions. — David Rodríguez - dribeas
– David Rodríguez - dribeas, Commented Apr 19, 2013 at 14:43
@DavidRodríguez-dribeas: and let's not forget that a class can be used as a template parameter, whilst a namespace cannot. — Matthieu M.
– Matthieu M., Commented Apr 19, 2013 at 14:48

Alok Save · Accepted Answer · 2013-04-19 14:21:37Z

10

There is no difference. static on the function declaration applies to the function.
An this pointer will not be implicitly passed to this function, So you cannot access non static class members inside this function without explicitly passing the object to it.

To remove the static first you should know and understand the purpose that it is designed this way. Without taking that in to consideration you are just bound to create a code smell of vast proportions.

answered Apr 19, 2013 at 14:21

Alok Save

208k56 gold badges448 silver badges539 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Rasmi Ranjan Nayak Over a year ago

Is there any difference between static int i vs int static i?

GuLearn Over a year ago

Please see my comment under the question. I think I'm doing the right thing

Alok Save Over a year ago

@RasmiRanjanNayak: None, apart from confusing the one who will maintain it.

Alok Save Over a year ago

@user2207811: If you have a class with no data members and only static functions you are much better off using an Unnamed namespace

Ben Voigt Over a year ago

@Alok: No, an unnamed namespace is a terrible solution. A class is accessible from multiple compilation units. So is a named namespace.

|

Mats Petersson · Accepted Answer · 2013-04-19 14:39:50Z

Yes, in the first case, the keyword static comes before the type int, in the second, they are the other way around. However, like many things in C and C++, there is no semantic difference. So, other than "cosmetically", there is no difference.

I'm not sure why you would want to remove static in classes as a general rule - there is probably a good reason a member function is declared static.

Collectives™ on Stack Overflow

the position of the static keyword in member method declaration

2 Answers 2

6 Comments

1 Comment

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

1 Comment

Linked

Related