In C++, a struct and a class are the exact same thing except structs default to public access while classes default to private. I believe at one point classes were more complex, but not anymore. I am pretty sure opengl can be used for 2d graphics as well as 3d graphics.

struct and classes are basically the same. The only thing that''s different is that (without using access specifiers) the members of structs are public and those of classes are private.

If you want to use structs instead of classes it''s fine, but I do believe most people prefer using class for genuine datatypes and struct for small, simple types.

Oh yeah, OpenGL can be used to to 2D graphics.

Now note this important issue:

The ONLY difference in C++ between classes and structs is that a struct''s member variables and methods are public by default, where they are private for classes.

Otherwise, they are the same. Structs can hold methods, constructors, overloaded operators, etc...

From my experience and just plain preference I use classes for data that needs to be abstract to go with the OOP paradigm, while I use structs where data needs to be out in the open.

Take this as an example:

If you wish to create a very simple rect class, the most convenient way for any user to acces elements in it is to make them public, thus you will have a x, y, w and h element that is public. (top, left, bottom and right if you prefer)
Now, since there is no need at all to encapsulate the data in a simple rect, you can use a struct by default, so that users know that the data structure is a open entity where all objects are public.
Of course, you can also add a constructor to this struct for easy initialization and some helpful methods such as Area, Width, etc... But make them all public.

I use this simple rule of thumb: "If you have to use either of the keywords; private, public or protected, in the declaration of the datatype, go with a class. If you want ALL data to be public by default use a structure."

Hope that helps.

I am assuming that the difference between classes and structs has been adequately answered or researched.

I think you will find that in general, as has been my experience, that the common use for structs are to hold "simple" data types like the RECT struct mentioned above. When you want to encapsulate data types AND you want to encapsulate methods associated with those data types, you would use a class. Now, you can add methods to a struct, but generally people just don''t.

I think (opinion here, not fact) the only reason structs are still around in C++ is for compatability with standard C libraries which use structs and not classes. Originally C++ was just an extension or upgrade of C, although now has become it''s own beast, but who wants to rewrite all of that stuff into classes when it works fine the way it is anyway?