🚀 go-pugleaf

gomberg@wcf.com wrote:
> 
> This is goto-free and I think equally clear:>>>------------------------------------------------------------------------------
>   HEV    hev1, hev2, hev3;     /* Event semaphores */
>   HMTX   hmtx;                 /* Mutex semaphore  */
>   void  *ptr;
>   if DosCreateEventSem(0, &hev1, 0, FALSE) then do;
>    if DosCreateEventSem(0, &hev2, 0, FALSE) then do;
>     if DosCreateEventSem(0, &hev3, 0, FALSE) then do;
>      if DosCreateMutexSem(0, &hmtx, 0, FALSE) then do;
>       ptr = malloc(SOME_SIZE)
>       if ptr<>NULL then do;
>          /* Do some stuff here */
>          return TRUE; /* We did okay */ end;
>       DosCloseMutexSem(hmtx);  end;
>      DosCloseEventSem(hev3);  end;
>     DosCloseEventSem(hev2);  end;
>    DosCloseEventSem(hev1);  end;
>   return FALSE;
> 
> And I would assert my code is (1) a lot more PL/1-like and
> (2) a lot easier to understand.

1. I assume you have #define'd "do" and "end" as "{" and "}".
How do you encode "do {...} while(...);" ?
2. The extra semi-colons after each do & end don't achieve anything.
3. What does "<>" mean in C ?

Otherwise, this is one example where you can remove goto's without loss 
of speed and improve clarity.
This doesn't mean you should never use goto's.

-- 
Andrew Dalgleish
Senior Software Engineer
Axon Research, Pty Ltd
6 Wallace Ave
Toorak, VIC
3142
AUSTRALIA
Tel:	+61-3-9826-5538
Fax:	+61-3-9824-0083
Email:	andrewd@axonet.com.au