Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!wjh12!talcott!harvard!seismo!brl-tgr!ron From: ron@brl-tgr.ARPA (Ron Natalie) Newsgroups: net.lang.c Subject: Re: YAAO (yet another assignment operator) Message-ID: <6616@brl-tgr.ARPA> Date: Mon, 17-Dec-84 11:22:59 EST Article-I.D.: brl-tgr.6616 Posted: Mon Dec 17 11:22:59 1984 Date-Received: Tue, 18-Dec-84 07:06:36 EST References: <209@cmu-cs-k.ARPA> <529@vu44.UUCP> Organization: Ballistic Research Lab Lines: 23 > Dean Rubine asked for a ->= operator, but this > is quite impossible (if you try to keep the language > clean, of course). -> isn't an operator, it's a syntactical > construct, like . or [expr]. Sorry, my book says that "->", ".", and "[]" are the primary expression operators and have the highest priority. > Also, it would be awfull to implement. In a statement > p ->= next > you would have to keep the type of 'p' around, and also the > expression on the righthandside would not be an ordinary > expression, neither a lvalue nor a rvalue, but something wierd > (a 'selection expression'?). I don't understand this at all. Keep the type of 'p' around? This makes litle sense. You better keep the type of something you are storing into around, regardless of the type of expression. I agree, it sucks. Nowhere does it define assignment-operator as being =. It doesn't even say =. -Ron