Windows program==one big class.

Started by
13 comments, last by tHiSiSbOb 20 years, 3 months ago
Is there anything wrong with making a windows program one big class? What I mean is having a class that has everything in it (includeing the main loop).
----------------------------------------------------"Plant a tree. Remove a Bush" -A bumper sticker I saw.
Advertisement
Um, have you tried putting main inside the class? O___O

[edited by - nervo on January 17, 2004 12:11:20 AM]
Well, R2D22U2..
Why, yes I have.
----------------------------------------------------"Plant a tree. Remove a Bush" -A bumper sticker I saw.
Those are called God classes and usually aren''t well regarded.
--God has paid us the intolerable compliment of loving us, in the deepest, most tragic, most inexorable sense.- C.S. Lewis
quote:Original post by antareus
Those are called God classes and usually aren't well regarded.


Ok. Thank you. Can you tell me why though?
EDIT: Well, I did some research and it says that a god class is a class that has more than one purpose. The program I am writing is a simple map editor and everything done has to do with pretty much the same stuff. Is it still wrong to have a god class?
EDIT2: Also, this god class of mine has several other classes in it. Is it still considered a god class?
[edited by - tHiSiSbOb on January 17, 2004 12:27:20 AM]

[edited by - tHiSiSbOb on January 17, 2004 12:28:26 AM]
----------------------------------------------------"Plant a tree. Remove a Bush" -A bumper sticker I saw.
Why even bother making it a class then. Just use namespaces and functions, cause it looks like to me you''re using classes just for the sake of using classes. If you want to do it the proper way, check out this tutorial.
quote:EDIT2: Also, this god class of mine has several other classes in it. Is it still considered a god class?

Yes. God classes are named that way because they generally do more than one thing and/or they 'know' too much. In software engineering terms, the God class is coupled to almost all of the other classes, inhibiting maintainability. Usually God classes end up mangling presentation of data with the actual logic that is done on the data. Although that sort of thing is fine for quick, small programs, (think VB) it can become harder to maintain.

Decouple the two using something like signals and slots. I have an entire app that is based only on signals and slots. They are very robust and scalable.

[edited by - antareus on January 18, 2004 1:12:25 AM]
--God has paid us the intolerable compliment of loving us, in the deepest, most tragic, most inexorable sense.- C.S. Lewis
quote:Original post by tHiSiSbOb
Is there anything wrong with making a windows program one big class? What I mean is having a class that has everything in it (includeing the main loop).


There isn''t anything wrong with it if you are using C# or Java. The C++ language tends to disagree with this practice, however.

Colin Jeanne | Invader''s Realm
quote:Original post by Invader X
There isn''t anything wrong with it if you are using C# or Java.


o__O

"Everything is a class" != "it''s ok to use just one class". WTF.
It''s already been done. MFC is an object oriented wrapper around win32.

This topic is closed to new replies.

Advertisement