while (true) and for (; ; ) [modified]

[Chris Meech]

Would you be talking about an Alderson Loop[^]. :) While the Wiki article is not a definitive reference, it seems that the practical use of infinite loops are minimal. I'd recommend to avoid them entirely. :)

Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]

[RugbyLeague]

I use them although not often. I also often add an empty IDisposable to classes in C# because I like to wrap things in "using" :~

[Dave Parker]

Real men use "goto" :p

[Luc Pattyn]

break, return, yield, goto, throw, Application.Exit(), longjmp(), ... can all be justified given the right circumstances. :)

Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

[bob16972]

They are both handy from time to time (expression parsing and times when you don't know how many iterations will be needed). I personally prefer while(TRUE) so as not confuse any VB programmer that comes across my code.

[Nemanja Trifunovic]

wizardzz wrote:

What are your views on these?

Infinite tail-recursion is much nicer.

utf8-cpp

[TheGreatAndPowerfulOz]

RugbyLeague wrote:

IDisposable to classes in C#

That's silly. It serves no purpose, except obfuscation and misrepresentation, if you don't implement the IDisposable!

"If your actions inspire others to dream more, learn more, do more and become more, you are a leader." - John Quincy Adams "Let me get this straight. You know her. She knows you. But she wants to eat him. And everybody's okay with this?" - Timon

[Ian Shlasko]

Checking my production system, it looks like I've used while (true) in six places... #1: Background thread that continuously monitors a Named Pipe #2: Background thread that periodically checks for application updates #3: Background thread that uploads trades as they're queued #4: Background thread that watches for incoming messages from the server #5: Background thread that sends heartbeats to the server #6: Background thread that handles message routing ON the server Basically, all of them are intended to run throughout the life of the application... They all have a sleep or a wait handle, but otherwise just loop continuously... It's a useful construct. Yes, I suppose I could add a global "Shutting down" condition, but it just hasn't been necessary. They catch the thread abort, clean up in the 'finally', and are designed so as not to damage anything external if the shutdown interrupts them at any point.

Proud to have finally moved to the A-Ark. Which one are you in?
Author of the Guardians Saga (Sci-Fi/Fantasy novels)

[Chris Maunder]

Beat me to it!

cheers, Chris Maunder The Code Project | Co-founder Microsoft C++ MVP

[Chris Losinger]

i like em just fine, in things like state machines, where the endpoint is unknown. do{...}while(ok) is ok, too.

image processing toolkits | batch image processing

[AspDotNetDev]

I like to consolidate:

for (; ; MessageBox.Show("Hello")) ;

:rolleyes: And here's the best I could do in VB.net:

For i As Integer = 0 To 0 Step 0
Next

Like somebody else mentioned, they may have their uses in background threads.

[WikiLeaks Cablegate Cables]

[Christopher Duncan]

Nishant Sivakumar wrote:

what it's meant to do.

Hang the app with an endless loop? :)

Christopher Duncan Author of The Career Programmer Watch Bad Programmer! - Premieres May, 2011

[Nish Nishant]

Christopher Duncan wrote:

Hang the app with an endless loop?

Only on a single core machine :-D

Regards, Nish

---

New article available: Resetting a View Model in WPF MVVM applications without code-behind in the view My technology blog: voidnish.wordpress.com

[Christopher Duncan]

:laugh:

Christopher Duncan Author of The Career Programmer Watch Bad Programmer! - Premieres May, 2011

[Jun Du]

I don't find many situations where I must use either. Something like while(!done) gives you a control over whether and when to exit, normal or abnormal.

Best, Jun

[Mike Hankey]

I use the while(true) consistently...in embedded apps. (AVR)

If you are cross-eyed and have dyslexia, can you read all right? http://www.hq4thmarinescomm.com[^] JaxCoder.com[^]WinHeist - Windows Electronic Inventory SysTem

[CPallini]

Not always. In C applications, for instance, you may know in the middle of the loop that you've to exit and while you may skip the following statements with an if and then use the condition, I prefer an immediate break.

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]

[Lost User]

Same here, useful but risky in the wild.

Join the cool kids - Come fold with us[^]

[Wendelius]

One version I every now and then use is:

while (6 * 9 != 42)

This wouldn't cause an infinite loop since one (particular) day those will be equal :)

The need to optimize rises from a bad design.My articles[^]

[Member 96]

I just used while(condition); in a unit test to test an async method for retrieving a business object. I can't imagine a use for them in production code though.

---

There is no failure only feedback