Programming Forums > Application Development > C++

mrynit · May 25th, 2006, 11:22 PM

Quote:

Originally Posted by Varrickmana

DaWei, why do you build me up, just to tear me down, baby? lol

http://en.wikipedia.org/wiki/BDSM

Jimbo · May 25th, 2006, 11:26 PM

Quote:

Originally Posted by Game_Ender

Maybe I am too anal and OO minded, but I don't write procedural C++ programs. So I have one header file and one source file per class. For really small classes, about ten to twenty lines, that are just utility classes related to a larger class I will include them with that classes sources. It is quite hard to follow someones code if they haphazardly group classes in source files. Now of course C is a whole other story.

Similar case here

King · May 25th, 2006, 11:39 PM

Quote:

Originally Posted by Prm753

Since none of my projects has gone over 5000 lines, I generally stick with 1 or 2 (at the most) source files. :p

You really need to make more files then. Each class should be going in seperate files.

Jimbo · May 25th, 2006, 11:52 PM

Quote:

Originally Posted by King

You really need to make more files then. Each class should be going in seperate files.

That's assuming he has lots of (or any) classes. Remember C++ can be procedural too. Even so, I'd try to split it up at that point, even if for nothing other than compilation reasons like DaWei mentioned.

Toro · May 25th, 2006, 11:59 PM

I usually create a lot of classes with in turn into a lot of different sources, :p . I also am a OOP minded person.

DaWei · May 26th, 2006, 6:28 AM

Quote:

...OO minded, but I don't write procedural C++ programs....Now of course C is a whole other story.....

I'll take issue with this expression of incipient guru-masterness. It's not an attack, I've said it before. OO is not new. Oog used it when he designed the wheel, and he didn't have classes. Mechanical engineers and hardware logic designers use it all the time (without "classes"). When OO is indicated, one uses it. When it's not, one uses the procedural approach. C or C++ be damned. A lawnmower is an object. It is not a member of your lawn object, nor is mowing a method of your lawn object. You bring your lawnmower to the lawn and do the job procedurally.

Game_Ender · May 26th, 2006, 8:52 AM

For better or for worse, right now I am at the stage where I see everything through object oriented glasses (drunken the coolaid so to speak). So if am I using a language that allows easy object oriented development I will use that method. I listed C as an example of a language I program procedurally in. You can of course to procedural in C++ and OO in C, or a mix of both.

I haven't done large C projects but I assume you break functions into groups (modules) that accomplish one task and create a header source file pair for them. So my "one class, 2 files" approach makes no sense in C.

DaWei · May 26th, 2006, 9:27 AM

To my way of thinking, OO is not a software discipline. It's a natural approach to any design that often (not always) results in a more effective and useful "thing". No point in repeating myself here, but you can see some thoughts at the link, "Why OOP, My View", in my signature.

View Poll Results: How many source files do you use in your projects?
Tons!	5	26.32%
A "medium" amount.	5	26.32%
A few.	3	15.79%
One or two.	6	31.58%
Voters: 19. You may not vote on this poll

May 26th, 2006, 9:27 AM	#18
DaWei Resident Grouch Join Date: Jun 2005 Posts: 6,453 Rep Power: 10	To my way of thinking, OO is not a software discipline. It's a natural approach to any design that often (not always) results in a more effective and useful "thing". No point in repeating myself here, but you can see some thoughts at the link, "Why OOP, My View", in my signature. __________________ Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

May 25th, 2006, 11:59 PM	#15
Toro Hobbyist Programmer Join Date: Apr 2006 Posts: 136 Rep Power: 0	I usually create a lot of classes with in turn into a lot of different sources, :p . I also am a OOP minded person.

May 26th, 2006, 8:52 AM	#17
Game_Ender Professional Programmer Join Date: May 2006 Location: Maryland, USA Posts: 306 Rep Power: 3	For better or for worse, right now I am at the stage where I see everything through object oriented glasses (drunken the coolaid so to speak). So if am I using a language that allows easy object oriented development I will use that method. I listed C as an example of a language I program procedurally in. You can of course to procedural in C++ and OO in C, or a mix of both. I haven't done large C projects but I assume you break functions into groups (modules) that accomplish one task and create a header source file pair for them. So my "one class, 2 files" approach makes no sense in C.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Programming Forums > Application Development > C++

Multiple Source Files in a Project