Declaring classes in global space

I have made a class but the problem is I want to create the class in global space (not inside main) but I can't do it like:

ClassName test(hwnd);

Because I don't even know what hwnd is yet. So how would I declare it in global space but still be able to do the code above, if you get what I mean?

Code:

---

ClassName *test = NULL;

int main()
{
    ...
    test = new ClassName(hwnd);
    ...
    delete test;
}

---

Quote:

---

Originally Posted by Rune Hunter

I have made a class but the problem is I want to create the class in global space

---

Why?

Quote:

---

Originally Posted by Dave_Sinkula

Why?

---

Echo that!

but:

Code:

---

Classname test;

int main()
{
  //....
  test.somefunc(hwnd);
}

---

Why? Sorry that is my fault, I didn't mean main. I am using win32 main function so I also have the windows callback for the messages.

Well to make it simple, to use it in differnet parts of the program.

Pass a pointer instead?

Hmm pointers didn't work, couldn't find any functions inside the class. I'm looking into anouther way of doing this though.

Quote:

---

Originally Posted by Thantos

but:

Code:

---

Classname test;

int main()
{
  //....
  test.somefunc(hwnd);
}

---

---

Ya that is how I am going to do it.

Quote:

---

Originally Posted by Rune Hunter

Hmm pointers didn't work, couldn't find any functions inside the class. I'm looking into anouther way of doing this though.

---

Hm.

Code:

---

#include <iostream>
#include <windows.h>

class whatever
{
public:
  void init(HWND *hwnd) {}
  void foo()
  {
      std::cout << this << std::endl;
  }
};

int main()
{
    whatever thing;
    thing.init(0);
    thing.foo();
    return 0;
}

/* my output
0012FF84
*/

---

Actually having classes in global space is not all that bad. I do this for my D3D Apps because it is easier to shut the system down if the class objects are global. You don't have to do it this way, but I find it easier.

Objects like Keyboard, Mouse, Device, Sound, are all global in my app. Note that only the instance of these classes is global but the definitions are in standard C++ header files and use a lot of object oriented techniques.

Where you instantiate your objects or how visible you want them to be is purely up to you and is more based on application structure more than a right or wrong way to do things.

Use what works.

using "class in global space" is not really object-oriented!
The true essence of C++ is object-oriented...then why not use it!
Use oop techniques, and you will find your way of programming to be better ;)

Having a global object don't make something not OOP.

Quote:

---

The idea behind object-oriented programming is that a computer program is composed of a collection of individual units, or objects, as opposed to a traditional view in which a program is a list of instructions to the computer. Each object is capable of receiving messages, processing data, and sending messages to other objects.

---

It doesn't matter where the object resides as long as you are only using the interface its all good.

Quote:

---

Originally Posted by Bubba

Actually having classes in global space is not all that bad. I do this for my D3D Apps because it is easier to shut the system down if the class objects are global. You don't have to do it this way, but I find it easier.

Objects like Keyboard, Mouse, Device, Sound, are all global in my app. Note that only the instance of these classes is global but the definitions are in standard C++ header files and use a lot of object oriented techniques.

Where you instantiate your objects or how visible you want them to be is purely up to you and is more based on application structure more than a right or wrong way to do things.

Use what works.

---

Ya that is what I am doing, don't ask why I didn't just explain I was making a d3d classes before, I havn't been thinking clearly lately.