Re: Complex accept method definition question

• To: curt@eraserhead.jpl.nasa.gov (Curt Eggemeyer)
• Subject: Re: Complex accept method definition question
• From: moon@cambridge.apple.com (David A. Moon)
• Date: Mon, 02 Dec 91 17:06:41 EST
• Cc: clim@BBN.COM, slug@Warbucks.ai.sri.com

You don't need to do anything special to allow the user to back up
and edit.  Everything typed at the outermost call to ACCEPT is supposed
to be editable.

If you read the documentation of activation and blip characters, you should
define the delimiters between recursive ACCEPTs as blip characters (i.e.
spaces and parentheses, or whatever syntax you choose) and leave the
activation characters alone.  If you use space as a blip character for
your own recursive calls to ACCEPT, and your presentation type is used
as the type of an argument to a command, then you need to think about the
interaction between that use of space and the command processor's use
of space as a blip character for its recursive calls to ACCEPT to read
the arguments to a command.

0,,

• Prev: reordering command menu items
• Next: CLIM 2.0 specs?
• Index: CLIM Mailing list (5-Oct-90 to 31-Dec-91)
• Thread: CLIM Mailing list Index (5-Oct-90 to 31-Dec-91)