C#

Dave Kreskowiak wrote:

Constants are only stored once, like a static.

Dave Kreskowiak wrote:

Even if you have 1,000 constants in a class and a thousand objects created from that class, you're still only using 4K for the constants.

Dewald wrote:

The reason I steered away from constants is because that would take up memory.

Guffa wrote:

I prefer using an enum rather than constants in a case like this, as an enum says a lot more about what a method returns than an int does. When a method returns an enum value, you don't have to read a lot of documentation to find out what constants to use to compare the return value with.

If you want the int value you can easily cast the enum to int, and use that with any existing code that requires an int.

sneha01 wrote:

Com.ExecuteNonQuery();

bool GetHandle;<br />
			GetHandle= false;<br />
			// Wait for 100 MillliSecond Before Get the Handle <br />
			int WaitingTime = 100;<br />
			Process pr = Process.Start("NotePad.exe");<br />
			while (GetHandle)<br />
			{<br />
				if (pr.StartTime.Ticks <= (DateTime.Now.Ticks - WaitingTime))<br />
				{<br />
					 GetHandle = true;<br />
				}<br />
			}<br />
			// Getting Handle ( as String just to know it's value )<br />
			MessageBox.Show (Handle.ToString());

Process newProc = Process.Start(newProcessInfo);
newProc.WaitForInputIdle();