Message-Id: <9302162321.AA21773@Athena.MIT.EDU>
To: jud@ceci.mit.edu, aybee@ceci.mit.edu
Date: Tue, 16 Feb 93 18:21:15 -0500
From: Adam Feder <aybee@ceci.mit.edu>


:= changed to =
@= changed to =@
added |>

forward became:
 forwardStatement:
  ATforward sendMsgExpr ';' 
      { $$ = new NodeState("forward",$2); }
  |
  ATforward ATsynchSend expression ';'
      { $$ = new NodeState("forward",$3); }
  ;

and sendMsgExpr's associate to the left:
 sendMsgExpr:
  sendMsgExpr ATsynchSend logicalOrExpr  { $$ = new NodeState("=>",$1,$3); }
  |
  sendMsgExpr ATasynchSend logicalOrExpr  { $$ = new NodeState("|>",$1,$3); }
  |
  logicalOrExpr  { $$ = $1; }
  ;

    
now, is the following right?:

  anonymousDeclaration:
	ATanonymous instanceDeclarations optBaseClassList classBody ';'
  ;

  instanceDeclarations:
	ATid
	|
	instanceDeclarations ',' ATid
	;

compare to classDecl...
	(are we not allowing instances when decl. class?
	 i think we ought not...but im checking)

 classDeclaration:
  ATclass newClass optBaseClassList classBody ';'
      { $$ = new NodeState("class",$2,$3,$4); }
  ;


and there was something else...but i wont remember til after ive sent this...
actually ive remembered!!!
	unless you have an objection, im placing "class" in the group
	of "handle operators" (new, delete, clone...)
	it will return the handle of the class obj associated with its arg.
	(q: is this bad? now user can syntactically write 
		"delete class Button")
	the other alternative i see is to make "class" forms of all functions
		where it should be allowed....such as "{} => class Button"
		but this seems restrictive, esp. considering our soon-to-be
		wide use of class objects for error-handling
	(thoughts?)
	im waiting on adding it til i hear back from you....
		
ab