Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!seismo!sundc!hadron!jsdy
From: jsdy@hadron.UUCP
Newsgroups: comp.lang.c
Subject: Re: Long Branches
Message-ID: <449@hadron.UUCP>
Date: Thu, 5-Feb-87 07:34:54 EST
Article-I.D.: hadron.449
Posted: Thu Feb  5 07:34:54 1987
Date-Received: Sat, 7-Feb-87 12:30:14 EST
References: <3950007@nucsrl.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 27
Summary: Not overly helpful, I'm afraid.

In article <3950007@nucsrl.UUCP> ram@nucsrl.UUCP (Raman Renu) writes:
>   I have a problem in using the C compiler and VAX assembler in our local
>4.3BSD(VAX) site.  I have a program which has a huge(>900lines) switch
>statement.
>The assembler chokes on (>32K long) long branches.

We had this problem on an Altos [29]86, 8086 Xenix machine.
Never thought that I'd see it on a Vax!  The compiler should
correctly interpret this.  However, the only portable solution
we could figure out that was (relatively) quick and easy was
to translate the case into if/else if/else if/ ...

Speaking of which, I'd like to promote the use of the form:
	if (...) {
		...
	} else if (...) {
		...
	} else if (...) {
		...  ...
	}
instead of indenting each successive "if".  Where appropriate
only, of course.  This is advocated in one of the early C Style
books.
-- 

	Joe Yao		hadron!jsdy@seismo.{CSS.GOV,ARPA,UUCP}
			jsdy@hadron.COM (not yet domainised)