> If there's one or more args, the lambda is called with them.  But we were planning on a convention of having most lambda values not take any args to avoid complexity, so what should the above do when the value is a lambda and there are no args?  Being able to get the lambda could be useful; maybe have a special arg like #t call it without args?  That's ugly, have only just now been thinking about this, so I solicit suggestions.

I'd vote to do nothing special.

People who want to make a foreign error object with a lambda as one of
the values can wrap it in (lambda () the-lambda-i-want-to-return). Would
this cause a problem in some situation?

>     I think the best thing is foreign-condition-ref/procedure, which
>     does not take args.  It returns a procedure that does take args,
>     like this:

Why the extra complexity of an additional procedure?

I think your reading level precludes you from noticing the problem with
the long names and big words. That's 4 separate words in the name of one
procedure, and "foreign" and "ref" are the only ones whose complexity is
commensurate to the complexity of the task at hand.