🚀 go-pugleaf

chl@clw.cs.man.ac.uk (Charles Lindsey) writes:
>
>Well that is what I thougut when I first saw the example, and I was about to
>dash off an article like you have done. But then I looked again and saw
>*exactly* what it was doing.
>
>So if you believe there is a better way, please can we see it?

I have a potential solution: The sample below utilizes the "fall-through"
in C's switch-statement to undo what has been done in the reverse order
required.

Of course, using break is only _potentially_ nicer than a goto. At least
in this case.

- Tor Iver 

--- BEGIN included text ---

#define once while(0)

void main(void)
{
  int btracksteps=0; /* Used to keep a count for backtracking. */

  do
  {
    if (!doSomething())
      break;
    if (!doSomethingElse())
      { btracksteps=1; break; }
     /* ... */
  }
  once;

switch(btracksteps) {
  case 10: UndoSomethingWayDownInThePrecedingCode();
      /* ... */
  case 2: UndoSomethingElse();
  case 1: UndoSomething();
 } 

}

--- END included text ---
-- 
Tor Iver Wilhelmsen <toriver@pvv.unit.no> Approx. M. Sc. in CS from NTH, Norway 
Siviling. Tor I. Wilhelmsen // c/o ESD Nordic // Postboks 226 // 1411 Kolbotn
All opinions above invisible unless expressed or put in a blender. Whatever.
Info: http://www.pvv.unit.no/~toriver/  Member of The Software Workshop, NTNU