i think you should use int instead of bool for return types of funcntions. Lets say that you have a function that does all the direct x initialization. Lets say one thing doesnt work so you return false. Now you have no idea what part of the initilization failed. You know that just part of it failed somewhere. It would be nicer to know what part. With ints you can go this. If it failes at the first part then return 1, second part then return 2.........no failures then return 0;
This way if your game fails then you can tell the client why. You can tell them that "You dont have a hardware accelerated 3D card" or "Your card doesnt support that resolution" instead of just saying "Initialization failure"


"I pity the fool, thug, or soul who tries to take over the world, then goes home crying to his momma."
- Mr. T

quote:Original post by ncsu121978
...This way if your game fails then you can tell the client why. You can tell them that "You dont have a hardware accelerated 3D card" or "Your card doesnt support that resolution" instead of just saying "Initialization failure"

This is why C++ has exceptions. Use them.

#include &ltexception>//void Initialize_Graphics(void){  HRESULT hr = Direct3D8Create(...);  if FAILED(hr)  {    throw new exception("Failed to create DirectGraphics object.");  }  ...}//// in your WinMain()...  try  {    Initialize_Graphics();    // other init functions  }  catch(exception &e) // catch all errors from preceding try block  {    MessageBox(..., e.what(), ...);  } 

Bah, I'm so stubborn and set in my ways I refuse to switch over to new types.

BOOL? No, bool!
DWORD? No, ulong! (typedef unsigned long ulong)
LPSZx? No! char*!

I should probably NOT do that for my OpenGL library too, but I still do. Portability isn't one of my strongpoints.

Edited by - Omaha on October 28, 2001 1:56:13 AM