Related articles |
---|
[6 earlier articles] |
Re: catch and throw, was Is multi-level function return possible? acolvin@efunct.com (mac) (2014-03-28) |
Re: catch and throw, was Is multi-level function return possible? ivan@ootbcomp.com (Ivan Godard) (2014-03-28) |
Re: catch and throw, was Is multi-level function return possible? kaz@kylheku.com (Kaz Kylheku) (2014-03-29) |
Re: catch and throw, was Is multi-level function return possible? kaz@kylheku.com (Kaz Kylheku) (2014-03-29) |
Re: catch and throw, was Is multi-level function return possible? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2014-03-29) |
Re: catch and throw, was Is multi-level function return possible? ivan@ootbcomp.com (Ivan Godard) (2014-03-28) |
Re: catch and throw, was Is multi-level function return possible? alan@scooby-doo.csail.mit.edu (Alan Bawden) (2014-03-29) |
From: | Alan Bawden <alan@scooby-doo.csail.mit.edu> |
Newsgroups: | comp.compilers |
Date: | Sat, 29 Mar 2014 02:44:24 -0400 |
Organization: | MIT Computer Science & Artificial Intelligence Lab |
References: | 14-03-065 14-03-068 14-03-070 14-03-076 14-03-078 |
Keywords: | errors, history |
Posted-Date: | 29 Mar 2014 13:58:12 EDT |
Kaz Kylheku <kaz@kylheku.com> writes:
> PL/I seems to have been influential in the design of Common Lisp conditions,
> right down to the terminology such as "conditions" being "signaled".
The current Common Lisp condition system is descended from the original
Lisp Machine Lisp condition system that was designed by guys who had
programmed in PL/I on Multics -- they were quite consciously borrowing
the terminology.
--
Alan Bawden
Return to the
comp.compilers page.
Search the
comp.compilers archives again.