Is this the most pointless code ever, or am I missing something?

Is there any point to doing this?

Code:

---

do
{
//Whatever code you want here
}
while (0)

---

Correct me if I'm horribly mistaken, but doesn't this loop do nothing? The code will run once and only once because it's a post-condition loop. Wouldn't this be exactly the same thing as just having the code within the loop by itself?

Yes. The Do While statement there is unnecessary. The literal integer basically ruins its purpose.

while loop correct

Kuphryn

There is a reason for that. If you have a #define like this:

Code:

---

#define swap(x,y) \
    do { \
        int t = x; \
        x = y; \
        y = t; \
    } while(0)

---

it mandatates a semicolon at the end of the call to swap:

Code:

---

swap(x, y);

---

If you just used regular { }, then you could get away with

Code:

---

swap(x, y)

---

It's just to make it look more like ordinary C code.

There was a thread about this somewhere a while ago. I can't seem to find it though. If you're interested, look through the search results for "while(0)".

[edit] I found it: http://cboard.cprogramming.com/showthread.php?t=66510 [/edit]

This construct is used for macros.

EDIT: Two minutes too late.

That sounds like a really horrible hack in this day and age of templates and generic programming.

The fact we need to use macros to explain that loop is a sure sign the loop is useless.

i thought that kind of loop wouldnt run unless we had something like

Code:

---

do
{
//do whatever
}while(int != 4)

---

in that kind of format

This is a do while loop, not a while loop.

>The fact we need to use macros to explain that loop is a sure sign the loop is useless.
It's impossible to say without any relevant context. I can think of several ways to justify that code by changing the context.

Quote:

---

Originally Posted by Prelude

>The fact we need to use macros to explain that loop is a sure sign the loop is useless.
It's impossible to say without any relevant context. I can think of several ways to justify that code by changing the context.

---

I'd be interested to see that actually. Honestly curious, not being snide :).

Well, I would also like to see exactly in which context that loop can be useful.

The macro context was already given.

How about a text book or tutorial? Such an example would be a good way to describe the workings of loop conditions in general (with the false condition) and the do..while loop by showing how it always runs once.

What about evolving code where it's likely that the body will become a loop but not quite yet?

What about debugging, where only a single iteration is required?

Quote:

---

Originally Posted by Prelude

The macro context was already given.

How about a text book or tutorial? Such an example would be a good way to describe the workings of loop conditions in general (with the false condition) and the do..while loop by showing how it always runs once.

---

Good point, that would be good for a tutorial.

Quote:

---

Originally Posted by Prelude

What about evolving code where it's likely that the body will become a loop but not quite yet?

---

Also a very good point, and thinking about it, I have done this in my own work.

Quote:

---

Originally Posted by Prelude

What about debugging, where only a single iteration is required?

---

I'm a bit wary on this, but I profess I wouldn't think about this either. I would prefer more a simple if statement, but I can see where this has merit in certain applications. Something to think about. Thanks! :)

Oh. I thought you were talking about situations in which the code would make sense.

I'm not even sure anymore why we are discussing this... Sure, I agree with you and I can add more... however the truth of the matter is that this is the 14th post on a subject that has only one answer:

That loop is useless. Does nothing.