multiple values

[Norman Adams <adams%tekchips.tek.csnet@CSNET-RELAY.ARPA>]

The language syntax and procedure library both favor calling with multiple
arguments over returning multiple values (no surprise considering that we
haven't have multiple return values in the language).  

I seems to me easier to fix the procedure library than the syntax.  
(Anyone want to adopt the "{...}n" notation that Steele mentions
in "The Ultimate Declarative"?)

Gary's survey identifies some rough edges that adding multiple values
causes.  I favor:

 a) changing call-with-current-continuation as described in 5a
    (call/cc creates n-ary procedures that invoke the continuation with as
    many arguments)

 b) using RECEIVE (or the equivalent), instead of the alternatives of
    either hacking up all the  binding forms, or adding a bunch of 
    new binding forms.

 c) living with it until we have more experience.

I'm for no coersions, no multiple-value-call.

-Norman
-------