Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site unisoft.UUCP Path: utzoo!watmath!clyde!floyd!harpo!ihnp4!zehntel!dual!unisoft!phil From: phil@unisoft.UUCP (Phil Ronzone) Newsgroups: net.lang.c Subject: Re: What Can't C Do? Message-ID: <237@unisoft.UUCP> Date: Mon, 19-Mar-84 16:13:40 EST Article-I.D.: unisoft.237 Posted: Mon Mar 19 16:13:40 1984 Date-Received: Wed, 21-Mar-84 01:09:44 EST References: <6900@unc.UUCP> <178@harvard.UUCP>, <237@opus.UUCP> Organization: UniSoft Corp., Berkeley Lines: 14 >> <> >> > While you're on the subject, what about == to compare two structures? >> > This is even more reasonable, in that structure assignment is supported... >> Yet another bad idea. This is much harder than it looks, for at least the >> following reasons: .... However -- comparing two structure of identical names is useful. Tells the compiler to do byte-for-byte compare inline. Equality and inequality are obvious, but I wouldn't want to count on < or >. Just to provoke net.lang.c.flame, how about my favorite extension to C? break(expr);