Simple game loop question

int main(){	bool fullscreen = true;	int ret;	if (MessageBox(NULL,"Message", "Start FullScreen?",MB_YESNO|MB_ICONQUESTION)==IDNO)	{		fullscreen=FALSE;		}	if (!window.Create(16, 800, 600, "Title", fullscreen))	{		Msg("couldnt load window");		return 0;	}	Init();	window.Show(true);	ShowCursor(false);	while (!exitgame)	{		ret = window.ProcessMsg();		if (ret == 0)			break;		if (ret == 1) 			DoFrame();	}	DeInit();	ShowCursor(true);	window.Destroy();	return 0;}

int main(int argc, char** argv){    Application app;    app.CreateWindow("The Demo",800,600, /*fullscreen=*/ false);    app.Initialize();    while (app.isRunning)       app.Run();    app.DeInitialize();        return 0;}

void main(){	bool running = true;	MSG	msg;	while (running)	{		if (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))		{			TranslateMessage(&msg);			DispatchMessage(&msg);		}		else 		{			//render stuff here		}	}}

/** inspired by http://www.flipcode.com/cgi-bin/fcarticles.cgi?show=63823 *//** Main Loop with Fixed Time Steps by Javier Arevalo */void Game::loop(const LL_DWORD TICK_TIME, const int MAX_LOOPS) {	LL_DWORD time0;	LL_DWORD time1;	LL_DWORD frameTime;		m_running = true;		LMINFO("Entering gameloop");		time0 = getTickCount();	do {		time1 = getTickCount();		frameTime = 0;		int numLoops = 0;			/*			The concept behind this is forcing every game logic tick to represent a			fixed amount of real-time (real-time is the time shown on your wristwatch).			Of course, ticks better take less CPU time to execute, than the real-time			it represents.		*/		while((time1-time0) > TICK_TIME && numLoops < MAX_LOOPS) {			gameTickRun(TICK_TIME/LL_REAL_VALUE(1000.0));			time0 += TICK_TIME;			frameTime += TICK_TIME;			numLoops++;			// Could this be a good idea? We're not doing it, anyway.			// time1 = getTickCount();		}			/*			This is where we gather user input and update the whole user interface			and perform general housekeeping. :) Things that don't need to be run at			a precise real-time speed. Since we want our game logic to be perfectly			deterministic, the things executed here (or during rendering) must not			affect the fixed-step game logic, in any way. In fact we have a run mode			where we record the user commands to a file, and we can play back these			commands entirely within the timestep loop above. This is an invaluable aid			for debugging, and is the basis for the lockstep network model we employ.		*/		if( frameTime != 0 ) {			independentTickRun(frameTime/LL_REAL_VALUE(1000.0));		}			// if playing solo and game logic takes way too long, discard pending time		if( !m_isNetworkGame && (time1-time0) > TICK_TIME ) {			time0 = time1 - TICK_TIME;		}			/*			This litte thing allows us to interpolate the positions, orientations,			etc of the visuals, in between game ticks. It smooths the visual aliasing			caused by a non-constant framerate. Which is the case, because we run a game			logic tick 15 times per second (TICK_TIME = 1000/15), while displaying at			framerates in the range 20-60 frames per second (fingers crossed). 		*/		if(m_canRender) {			// account for numLoops overflow causing percent > 1			LL_REAL percentWithinTick = lunarlady::math::min(LL_REAL_VALUE(1.0), LL_REAL(time1-time0)/TICK_TIME);			drawWithInterpolation(percentWithinTick);		}	} while ( !m_stateManager.empty() && m_running);}

while (running){   while (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))   {      TranslateMessage(&msg);      DispatchMessage(&msg);   }   //render stuff here}

while (running){   if (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))   {      TranslateMessage(&msg);      DispatchMessage(&msg);   }   else    {      //render stuff here   }}