Andy Wingo scripsit:

> There is also the approach of using no type at all and returning the
> values on the stack.

Indeed, though that can lead to very strange behavior.  For example,
if the identifier "map" is known to be bound to its R5RS definition, a
compiler can reject (map (foo)) as erroneous, but under a "return on the
stack" implementation, (foo) might return both the function and the list
to map.  I think it was Henry Baker who pointed this out.

--
They do not preach                              John Cowan
  that their God will rouse them                cowan@ccil.org
    A little before the nuts work loose.        http://www.ccil.org/~cowan
They do not teach
  that His Pity allows them                         --Rudyard Kipling,
    to drop their job when they damn-well choose.   "The Sons of Martha"

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports