Thread: A few questions on game programming

Hey all, I'm working on a game with a few friends but I'm the one that is doing pretty much all the actual programming. The others are doing art and some other stuff that we need for the game. My main question is:

I know that the main() should never really be that big but I am at a loss of how to shorten it up. Is it a huge standard to keep the main() down under 100 or is there an exception in game programming?

This being my first full game, I want it to be cross platform. Is allegro fully compatible with both linux and windows. I am programming in FC 10 and my friends are using windows. Is there any way to be sure that when i send them the code it will work in windows as long as I am not using any linux specific functions.

If there is any other comments you would like to make on standard game programming practice please feel free to do so.

Thanks all.

My main:

Code:

//
// WinMain
//
int WINAPI WinMain(HINSTANCE hInstance,
                   HINSTANCE prevInstance, 
                   PSTR cmdLine,
                   int showCmd)
{
    //Create window for app
    //Load settings from INI
    INIReader *pReader = 0;
    try
    {
        pReader = new INIReader();
        pReader->LoadAndParse("..\\INI\\Options.ini");
    }    
    catch (INIReader::INIFileError &err)
    {
        err;
		::MessageBox(0,"Cannot open INI file",0,0);
        return 0;
    }
    
    int iWidth = pReader->GetInt("Display","ScreenWidth");
    int iHeight = pReader->GetInt("Display","ScreenHeight");   

    //Really need to make an ini function to get a bool from the file
    bool bWindowed = false;
    int result = ::MessageBox(0,"Do you wish to run in fullscreen mode?","Screen mode",
                              MB_YESNO | MB_ICONQUESTION);

    if (result == IDNO)
    {
        bWindowed = true;
    }
    
    pReader->Cleanup();
    delete pReader;
    
    SpaceXApp::CreateInstance();

    //Start the app by initializing D3D
    if(!SpaceXApp::GetInstance()->InitD3D(hInstance,
        iWidth, 
        iHeight, 
        bWindowed, 
        D3DDEVTYPE_HAL,
        "SpaceX application",
        true))
    {

        ::MessageBox(0, "InitD3D() - FAILED", 0, 0);
        return 0;
    }

    try
    {
        //Setup the app			
        if(!SpaceXApp::GetInstance()->Setup())
        {
            ::MessageBox(0, "Setup() - FAILED", 0, 0);
            return 0;
        }
    }
    catch (X3DException &e)
    {
        e.ShowError();
    }
    catch (std::exception &e)
    {
        SpaceXApp::GetInstance()->Cleanup();
        ::MessageBox(0,e.what(),"UNKNOWN EXCEPTION CAUGHT",MB_OK | MB_ICONEXCLAMATION);
        std::cout << e.what() << std::endl;
    }
    
    //Start the loop
    SpaceXApp::GetInstance()->EnterMsgLoop();

    //If we get here, we are done
    //Clean up the memory and COM objects
    SpaceXApp::GetInstance()->Cleanup();

    //Ok Windows, it's all yours
    return 0;
}

I should break out the sections into functions but haven't yet. My main then would consist of about 4 functions.

Is there any way to be sure that when i send them the code it will work in windows as long as I am not using any linux specific functions.

The APIs are different and the calls are different. It will be more of a 'how do I do this in Linux/Windows' question when porting between the two. API calls for Win32 won't work in Linux.

The best way in my opinion is to define an interface that will not change and will define the behavior of the application. Then the implementation can be in Linux or Windows and as long as the interface does not change it will not break either of you.

Thanks for the quick reply. I'm am working now into further breaking my main down into functions. Since I am using allegro It seems a lot of the stuff you have in your main is taken care of for me. Is that right?

wouldent mind seeing this ini parser


int iWidth = pReader->GetInt("Display","ScreenWidth");
int iHeight = pReader->GetInt("Display","ScreenHeight");

how do you make it read titles from a ini and not have to loop through the whole thing?

Main:
- Use a class to process command line options.
- Use a class to process ini settings.
- Use a class to initialize/store game components (keyboard, mouse, gui, graphics, database, network, files).
- Start the game loop (usually a method of the last class).
- Cleanup

Game Loop:
- Logic, graphics, input, etc.

It's all abstracted, so it should be pretty short. Shorter if you use and wrap wxWidgets or something instead of win32 api.