caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Brown <caml@davidb.org>
To: padator@wanadoo.fr
Cc: caml-list <caml-list@yquem.inria.fr>,
	Damien Guichard <alphablock@wanadoo.fr>,
	Florian Weimer <fw@deneb.enyo.de>
Subject: Re: [Caml-list] The Caml morale crasher #1
Date: Thu, 08 Sep 2005 09:44:53 -0700	[thread overview]
Message-ID: <1126197893.3685.7.camel@a64.davidb.org> (raw)
In-Reply-To: <9504834.1126184133428.JavaMail.www@wwinf1536>

On Thu, 2005-09-08 at 14:55 +0200, yoann padioleau wrote:
> > * Damien Guichard:
> > 
> > > When annoucing an OCaml project on a public forum i have been
> > > advised to renunce lambdas because it would impede translation to "a
> > > less obscure, more popular language".
> > 
> > Most languages offer strictly downward closures.  Even GCC's C
> > implementation has them. 8-)
> 
> Again I think I will disagree on the choice of your words :)
> GCC has nested functions. I think that we can't call that a closure; a closure is something
> that close his environment and store it somewhere. There is no such thing in GCC I think.

GCC definitely implements downward closures.  You can take the address
of nested functions, and as long as the stack frame is still valid, they
have access to values defined in the enclosing function.  GCC implements
this by generating trampolines on the stack and passing the address of
the newly generated code as the function pointer.  It fails to work on
platforms that have security features that prevent stack execution.

Dave


  parent reply	other threads:[~2005-09-08 16:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08 12:55 yoann padioleau
2005-09-08 16:35 ` skaller
2005-09-08 16:44 ` David Brown [this message]
2005-09-08 17:14   ` Florian Weimer
  -- strict thread matches above, loose matches on Subject: below --
2005-09-01 16:32 Damien Guichard
2005-09-03  6:06 ` Erik de Castro Lopo
2005-09-07 11:58 ` Matt Gushee
2005-09-07 18:06   ` Damien Guichard
2005-09-07 18:06   ` Damien Guichard
2005-09-08 12:46 ` Florian Weimer

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=1126197893.3685.7.camel@a64.davidb.org \
    --to=caml@davidb.org \
    --cc=alphablock@wanadoo.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=fw@deneb.enyo.de \
    --cc=padator@wanadoo.fr \
    /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;
as well as URLs for NNTP newsgroup(s).