Subject: @foo me is <value>

From: [email-masked]
Date: Wed, 30 Dec 1992 11:53:35 -0800

The message syntax is really handy.  

(You can just create a property named foo_msg, and then the server
automatically interprets "@foo <object> is <message>" to let you set the
foo_msg of anything you own.  Permissions are handled automatically.)

Here's my question:

Why not generalize this, and drop the need for adding "_msg" to the property
name?  (The slot would now be named "foo" instead of "foo_msg", and all slots
could be set in this fashion.)  This would be done last, so any existing @foo
verbs would take priority, if they exist.  The server would need to check the
type of the <value> and produce an appropriate error message.

What do people think?

-- Amy
	jaime@LambdaMOO
	[email-masked]