[669] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

Re: assignment operator

daemon@ATHENA.MIT.EDU (Tue Mar 7 17:34:32 1995 )

From: The Importance of Being Chuck <cadams@weather.Brockport.EDU>
To: crag@serial.mit.edu (Robert de Forest)
Date: Tue, 7 Mar 1995 17:28:40 -0500 (EST)
Cc: coldstuff@MIT.EDU
In-Reply-To: <m0rm69a-000KcEC@serial> from "Robert de Forest" at Mar 7, 95 02:46:48 pm

Robert de Forest drew these heiroglyphs:
> I'd like to propose '->' be the assignment operator. It visually represents
>  what happens to the variable being assigned the new value. It has no chance
>  of being pronounced, 'equals'. It looks cool...

it's backwards.  :) 

though that's been discussed.  What concerns me is that '=' is already
assignment.  do we really want two different assignment operators?  or
are we removing the single '=' entirely?  If so, all I'd do is write
code in-db that changed them back and forth like JHcore MOOs do with
comments.  which makes the whole issue of what to call it quite
academic, actually.  but it's not feasable to write code in-db that
does assignment-as-expression, so let's have it in the server.

> What have I left out?

how about index-as-lvalue?  (foo[bar] = 1; foo[bar..baz] = [1, 2, 3])