Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!natinst!rpp386!woody
From: woody@rpp386.cactus.org (Woodrow Baker)
Newsgroups: comp.lang.c
Subject: Re: problems/risks due to programming language
Summary: use a macro
Message-ID: <18034@rpp386.cactus.org>
Date: 26 Feb 90 12:53:14 GMT
References: <1597@awdprime.UUCP> <8133@hubcap.clemson.edu> <SUY1G_Fxds13@ficc.uu.net>
Organization: River Parishes Programming, Plano, TX
Lines: 20

In article <SUY1G_Fxds13@ficc.uu.net>, peter@ficc.uu.net (Peter da Silva) writes:
> 	switch(c)
> 	{
> 		case '0', '1', '2', '3', '4', '5', '6', '7', '8', '9':
> 			digit();
> 		default:
> 			not_a_digit();
> 	}
> 
I'd fire a programmer for code like this:

> a loop. I would suggest that 'break' be given a mandatory keyword argument:
> either 'break switch', 'break for', and so on.

So go define a macro to do that.

#define break_switch  break

Cheers
Woody