🚀 go-pugleaf

In article <4892se$np@news0.rain.rg.net>, Paul Long <plong@perf.com> writes:
>
 >Oh, I'm sure somebody'd find a use for it and really like it. Here's
 >how it could be (ab)used with an if statement.
 >
 >    void manipulate_the_windows(Window *top)
 >    {
 >        Window *A = NULL, *B = NULL *C = NULL;
 >
 >        if check_parms (top == NULL)
 >            break check_parms;
 >        else {
 >            do_something_with_window(top);
 >            A = get_subwindow(top);
 >            if (A == NULL)
 >                break check_parms;
 >
 >            do_something_different_with_window(A);
 >            B = get_subwindow(A);
 >            if (B == NULL)
 >                break check_parms;
 >
 >            do_something_with_window(B);
 >            C = get_subwindow(B);
 >            if (C == NULL)
 >                break check_parms;
 >
 >            /* All windows I'm looking for are good, so do it  */
 >            do_something_weird_with_four_windows(top,A,B,C);
 >
 >            return;
 >        }
 >
 >        /* Do error handling here */
 >    }
 >
>Ugly, huh, early return and all? People do this sort of thing, though.
>What the programmer is doing here would be better served by a labeled
>compound statement and breaks to leave it (or situation indicators).
>Gotos are currently used. IMO, though, the best solution would be to
>rewrite the logic as something more conventional.
>
>BTW, this example came from something someone posted to comp.std.c
>awhile back. Look familiar?

Very familiar. I much prefer the way I originally wrote it.

--

Chris Volpe				Phone: (518) 387-7766 (Dial Comm 8*833
GE Corporate R&D			Fax:   (518) 387-6560
PO Box 8, Schenectady, NY 12301		Email: volpecr@crd.ge.com