Re: Representing Closures in C
- From: "Tommy Thorn" <tommy.thorn@xxxxxxxxx>
- Date: 25 Jul 2006 00:41:04 -0400
Hans Aberg wrote:
However an elegant method, I am told that it hard to use in debugging,
as it is difficult for humans to interpret. So in actual functional
language implementations, it has not been used so much.
This is really no different than the problem of tracking source level
variables in the optimized assembly. A tedious task for humans, but
that's what compilers use symbol debugging entries (eg. DWARF2) for.
If it sees little application in practice it may have more to do with
the fact that it's still only a step on the road to an efficient
implementation.
Tommy
.
- Follow-Ups:
- Re: Representing Closures in C
- From: Hans Aberg
- Re: Representing Closures in C
- References:
- Re: Representing Closures in C
- From: Johan Tibell
- Re: Representing Closures in C
- From: Hans Aberg
- Re: Representing Closures in C
- Prev by Date: Re: Why LL(1) Parsers do not support left recursion?
- Next by Date: Looking for compiler term project suggestion
- Previous by thread: Re: Representing Closures in C
- Next by thread: Re: Representing Closures in C
- Index(es):
Relevant Pages
|