quote:Original post by Sinner_Zero

SO in the end........

Theyre ususally isnt a difference in seed between struct and class unless virtual is used. And class might actually be faster in some cases.

and CobraA1 is in serious need of a comp, YOU CAN ATLEAST BUY A P 200 FOR LIKE $150 at a computer sale!

GOTO WWW.FUNCORP.CJB.NET

I got off as soon as I read about adult content - that generally tells me that the site is up to no good. Also, I am well aware that I can get computers for that cheap. As I said, I just fiddle around, so I really don''t need a new computer yet. All I need is something that can do papers and E-mail, and what I have does that very well.



"Science is a tool. If the tool works, we use it. If it''s true, that''s great, but if it isn''t, it doesn''t matter" -- ("Desert Fox" from GameDev.net)''s physics teacher

On a 486/66 virtual overhead could be somewhat significant...

...
Sinner Zero, Who ever told you that structs were faster than classes either didn''t know what they were talking about, or you left out a long list of qualifiers

...
And I found a marginal differnce in rendering speed using a single threaded win32 api app verus a multithreaded MFC app (<1% once I knew what I was doing.) K6-3 450MHz, TNT 16MB, 128MB, Win2000

...
The advantage of creating a OOD game engine is that it would allow you to adapt the system to additional platforms, incorporate new sub-system features, provide a foundation for he game design, and help maintain the code more-so than procedural code.

The disadvantage is slight performance impact, more ''sophisticated'' or maybe ''esoteric'' code (because many seem to favor procedural code), and a steeper learning curve.

...
A popular misconception (held by me not so long ago), is that you could easily emulate OOD techniques in C. The acutal case, is you can easily emulate procedural techniques in C++, and think you are doing OOP. A class without inheirence, with no virtuals, and/or no derived classes is just organized procedural code. Which doesn''t seem like a bad idea to me... but it''s not a reason C or C++ should be your preferred language.

I suppose you can (must!) implement some OOP code in C in order to use DirectX; specifically you must implement the vtable. So you could create inheirtance and OOD code in C using similar techniques. I''ve never done this, so I don''t know how hard or how big of an arse pain it is. I suspect it is easier, the first time, in C++.


...
I don''t know about the rest of you, but if I ever have to use a computer to do the same thing twice, I''m pissed.

I suspect that it is actually easier to create an engine using procedurally techniques, rather than OOD techniques. It''s much easier to use OOD code than it is to write it.

...
Imagine if Dx was procedural code, intellisense wouldn''t be so useful anymore You have to know the function you wanted to use before you use it, with the class you just type a . or a -> and it pops up on the screen for you