Thread: Run Error, Commands Executing Simultaneously..

I have a problem with the way my actual program runs. Ive included the code for the delay function that i wrote as well, although i know the function works fine by itself.

My problem is that when the code runs through it appears to do more than one command at the same time, and i need it to stop, finish all the current commands, then perform the next command.

Code:

#include <stdio.h>
#include <sys/time.h>

void Delay(double DTime);

void main()
{
	char Word[] = "Goodbye World\n";
	int Counter;
	
	printf("Hello");
	Delay(5.0);
	printf("World... ");
	
	printf("Good\n");
	Delay(5.0);
	printf("Day\n");
	
	for (Counter = 0; Counter < strlen(Word); Counter++)
	{
		printf("%c", Word[Counter]);
		Delay(0.5);
	}	
}

void Delay(double DTime)
{
	struct timeval TData, ETData;
	long Milliseconds, Seconds;
	gettimeofday(&TData, NULL);
	Milliseconds = ((DTime * 100000) - (int)DTime) + TData.tv_usec;
	Seconds = TData.tv_sec + (DTime / 1);
	if (Milliseconds > 999999)
	{
		Milliseconds -= 1000000;
		Seconds += 1;
	}
	for (gettimeofday(&ETData, NULL); ETData.tv_usec < Milliseconds; gettimeofday(&ETData, NULL));
	for (gettimeofday(&ETData, NULL); ETData.tv_sec < Seconds; gettimeofday(&ETData, NULL));
}

Now This Outputs The Following:
{5 Second Delay} HelloWorld... Good
{5 Second Later} Day
{0.5 Seconds Later} Goodbye World


Ive been at this all night, so before i go to sleep i figured i should ask the experts. You guys really seem to know your stuff so i thank anyone that took the time to even just read this. Its much appreciated.
Thank again, Raz

I think you should use the timer mechanism offered by the OS, or signals...this busy waiting isn't a very good way to create a timer. ie. your timer starts, and it should delay for 1 second, along comes some processes with higher priority than yours. your process is swapped out and doesn't get a chance to restart for 3 seconds. Your timer never comes. since it was swapped out, and wasn't allowed to update itself. Not to mention the processor could be doing alot better things than this. and also gettimeofday is a system call, which causes a switch to kernel mode in the processor, then a switch back once the call has succeeded, so its fairly expensive....and imagine the amount of times your calling it in say 5 seconds.