From: Kwangkeun Yi <kwang@ropas.kaist.ac.kr>
To: Pierre.Weis@inria.fr
Cc: skaller@maxtal.com.au, caml-list@inria.fr
Subject: Re: Question on language design (keywords vs Pervasives)
Date: Tue, 22 Aug 2000 09:38:05 +0900 (KST) [thread overview]
Message-ID: <200008220038.JAA10162@ropas.kaist.ac.kr> (raw)
In-Reply-To: <200008212124.XAA05094@pauillac.inria.fr> (message from Pierre Weis on Mon, 21 Aug 2000 23:24:47 +0200 (MET DST))
> I'm sure that there is no ``more primitive function'' than raise to
> raise an exception. So sorry, you cannot define raise ``in terms of a
> more primitive function'' in Caml. You would need a language with
> call/cc to express that, and Caml is not this language.
To make it precise, we don't even need call/cc.
Just a kind of cps transformation that carries two continuations (one
for normal continuation and the other for handler continuation)
removes all the raise/try expressions. The transformation is
well-known. See
@InProceedings{KiYiDa98,
author = "Jung-taek Kim and Kwangkeun Yi and Olivier Danvy",
title = "Assessing the Overhead of ML Exceptions by Selective
CPS Transformation",
pages = "103-114",
booktitle = "The Proceedings of the ACM SIGPLAN Workshop on ML",
year = 1998,
url = "http://ropas.kaist.ac.kr/~kwang/paper/98-ml-kiyida.ps.gz",
month = sep
}
-Kwang
--
Kwangkeun Yi http://cs.kaist.ac.kr/~kwang
next prev parent reply other threads:[~2000-08-22 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-18 2:07 Fermin Reig
2000-08-19 16:57 ` Frank Atanassow
2000-08-20 19:01 ` Pierre Weis
2000-08-20 19:55 ` John Prevost
2000-08-21 8:58 ` Pierre Weis
2000-08-21 19:47 ` John Prevost
2000-08-21 21:41 ` Pierre Weis
2000-08-21 16:44 ` John Max Skaller
2000-08-21 21:24 ` Pierre Weis
2000-08-22 0:38 ` Kwangkeun Yi [this message]
2000-08-22 2:25 ` John Max Skaller
2000-08-22 9:08 ` Pierre Weis
2000-08-22 8:31 ` Pierre Weis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200008220038.JAA10162@ropas.kaist.ac.kr \
--to=kwang@ropas.kaist.ac.kr \
--cc=Pierre.Weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=skaller@maxtal.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox