Ok, my past C++ experience has all been in the Windows environment using MFC so I've never really worried about a main(...) function as the App Wizard took care of all that for me.
When writing a console app with a main(...) function, is it ever reasonable to put main(...) in a class as a member function or should it always be kind of hanging out there as a global so to speak? If it can be put in a class, how does the OS know where the entry-point for the exe is?
I don't think you can put main() in a class (except in Java).
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
Just leave it global and have it call the class member function you want to run.
That's kind of what I figured I'd end up doing. Now for a twist on the question though, how do I model this type of program (for instance in Rational Rose)? The classes are easy, but how do you model the "global" stuff? This is probably the wrong forum to ask this.
