Related articles |
---|
Representing Closures in C johan.tibell@gmail.com (Johan Tibell) (2006-07-21) |
Re: Representing Closures in C haberg@math.su.se (2006-07-21) |
Re: Representing Closures in C tommy.thorn@gmail.com (Tommy Thorn) (2006-07-21) |
Re: Representing Closures in C johan.tibell@gmail.com (Johan Tibell) (2006-07-22) |
Re: Representing Closures in C wyrmwif@tsoft.org (SM Ryan) (2006-07-23) |
Re: Representing Closures in C haberg@math.su.se (2006-07-23) |
Re: Representing Closures in C tommy.thorn@gmail.com (Tommy Thorn) (2006-07-25) |
Re: Representing Closures in C tommy.thorn@gmail.com (Tommy Thorn) (2006-07-25) |
Re: Representing Closures in C haberg@math.su.se (2006-07-25) |
From: | "Tommy Thorn" <tommy.thorn@gmail.com> |
Newsgroups: | comp.compilers |
Date: | 25 Jul 2006 00:41:04 -0400 |
Organization: | http://groups.google.com |
References: | 06-07-05806-07-067 |
Keywords: | functional |
Posted-Date: | 25 Jul 2006 00:41:04 EDT |
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
Return to the
comp.compilers page.
Search the
comp.compilers archives again.