Search results

back on the old 486 and early pentium chips assembler was a valid choice for doing games, however modern chips are a nitemare to code on, multi-pipelines, out of order execution and other func techs mean that the stuff goes fast but its a nitemare to code, thus in 99.999% of cases it best left...

*up steps the experianced programmer* First up, C# isnt too slow for games, it has 95 to 98% of the speed of C++ apps thanks to the JITing which is done at first run time and given that in most games the bottle neck is the gfx card drawing rate that 2% doesnt make a huge difference :) C and...

*shakes head and walks off*

btw, i wouldnt count on being safe and not being sued, you still own stuff and have money yourself, so if they really wanted to and you didnt obey the 'stop ripping off our ideas' letter they could sue you and the members of your team (or at least the ones in areas where the copyright is...

yep, it can be done, i had something like it in Eradicators for a while, however it got removed due to design changes and it had some small bugs which i never got a chance to work out...

start a normal C++ (ie not managed) project

yep, i'd advise against using 'using namespace std;' as well as you get much better context infomation by typing std::cout etc and the same applies when making your own name space, access them via name::class/function. About the only time you can break that rule is if you are doing a VERY small...

you've got pre-compiled headers turned on in the IDE, look in the project options (cant remember where off hand) to turn them off

actualy, there is no good reason for the files to have a .h extension and iirc the C++98 standard drops them for the standard headers. I've even seen projects which use .hpp to indicate its a C++ header (which makes sense when you consider it, .c/.h for C and .cpp/.hpp for C++)

Its a popular misconception that OOP is automagicaly better/worse than anything else, as with all programming methods the best one is the one which best fits the problem at hand. Learn about them all by all means, but dont crowbar EVERYTHING into one method as sometimes its just not the correct...

dear god, over commenting hell. With something that simple at the most you need a comment on the line above and in most cases you dont need line by line commenting. If you was taught that then you've been taught bad habits yourself :)