OOP in windows

Why cant i do it in the plain simple old way?

CUSTOMCLASS OBJECT;
OBJECT.GetaFunction(0);

When programming windows, I have to do this mess, why?

MYCLASS *APOINTER = NULL;
APOINTER=new MYCLASS;
APOINTER->GetaFunction(0);


:confused:

No idea - it looks reasonable on the face of it.

Posting some real code and some real error messages would be better.

*im stuipid*

I found out... Looks like its illegal to define global objects. :D
(didnt know)

I'm not satisfied that you actually understand the problem, actually. If you post some code as Salem suggested perhaps we can set you straight.

It seems to me you find using pointers to be something of a foreign concept. And its perfectly legal to make global objects. You just couldn't do something like:

Example:

Code:

---


class OBJECT {
public:
  int whatever();
};

OBJECT o;
o.whatever();

int main(void) {
  return 0;
}

---

Since it would be illegal to call a member function in that manner.

are we talking MFC here?

This thread is old, but bah :D
No, we are not talking MFC, we are talking plain and simple C++
(Object Oriented Programming, shortend OOP), which was invented by scientists from Norway :D (My country ofcourse) ;)

I shall post the code, just to make you happy :D

Code:

---

#include "jumpClass.h"
JUMPCLASS jumpObject;
jumpObject.setJumper(0); // This line is illegal it seems

int WINAPI WinMain(...) {

return 0;
}

---

Will it be illegal as well, if I call it with a constructor? :)