4

Is it possible to access private members of a class in c++.

provided you don't have a friend function and You don't have access to the class definition

yesraaj
  • 46,370
  • 69
  • 194
  • 251

4 Answers4

8

You mean using some pointer arithmetic to gain the access ? It is possible but is definitely dangerous. Take a look at this question also: Accessing private members

Community
  • 1
  • 1
Naveen
  • 74,600
  • 47
  • 176
  • 233
6

I think there was some old school trick like this:

#define private public
#include "header.h"
#define private private

But you are strongly discouraged to do this (I've read quickly that the said something about this in the C++ standard) - if you want to read more about this google for "#define private public"

bernhardrusch
  • 11,670
  • 12
  • 48
  • 59
  • I've not defined a class in two header files. Is it possible to declare public members in one file and private in another and only deliver the public header? If so, we have absolutely no idea what else is in the class. – Les Apr 08 '09 at 12:23
  • You could use something like the PIMPL idiom http://www.gotw.ca/gotw/024.htm to hide the private parts – bernhardrusch Apr 08 '09 at 15:27
2

Well I might be talking rubish, but I think you could try to define a "twin" class with same members as the class you want to modify but different public/private modifiers and then use reintepret_cast to cast the original class to yours in which you can access the private members.

Its a bit hacky ;-)

A bit of code to explain the idea:

class ClassWithNoAccess 
{
public:
  someMethod();

private:
  int someVar;
};

class ClassTwin 
{
public:
  someMethod();

public:
  int someVar;
}

and somewhere in the code:

ClassWithNoAccess* noAccess = new ClassWithNoAccess();
ClassTwin* twin = reinterpret_cast<ClassTwin *>(noAccess);
twin->someVar = 1;

edit: so like someone already wrote before, this might work but the standard does not guarantee the order of the variables with public and private modifier will be the same

seq
  • 161
  • 4
  • You must be careful if you intend in going that way. Changing your private to public methods can turn a regular class into an aggregate or a POD, effectively changing how the compiler deals with it. – David Rodríguez - dribeas Apr 08 '09 at 13:13
2

Even if it were possible through some nasty hack - see earlier posts - you SHOULD not do it.

Encapsulation exists for a very good purpose, and setting class member as private means that the developer did not intend anyone to mess around with that member. That should mean

"You don't have to access this member in order to use the public interface to it's full intended extent"

Jukka Dahlbom
  • 1,740
  • 2
  • 16
  • 23