From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: ** X-Spam-Status: No, score=2.8 required=5.0 tests=DNS_FROM_RFC_POST, HTML_MESSAGE,SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id 68815BBAF for ; Tue, 24 Mar 2009 19:30:02 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuoCAKXDyEnRVdulmGdsb2JhbACCIjGSVj8BAQEBAQgJDAcRrUOPQQEDAQODcwaFaA X-IronPort-AV: E=Sophos;i="4.38,414,1233529200"; d="scan'208";a="24904770" Received: from mail-ew0-f165.google.com ([209.85.219.165]) by mail3-smtp-sop.national.inria.fr with ESMTP; 24 Mar 2009 19:30:01 +0100 Received: by ewy9 with SMTP id 9so2355701ewy.27 for ; Tue, 24 Mar 2009 11:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=y7uJSO4MK6YH/gILZbXt+Ewr2ElafXr6F5682JUV3/U=; b=Ub7+50udat2j90uIRqvINCW7SqkY8G1DMnzM36IZE+CyD7FKi/L6i/x2RCbWgn1qiF PGVtmd7iBppa/NH3pQ+ODHWqt3h6P7EWKO7/HZGnqPlPYGuKrU8PViApu4NBd3cW5YlA SjPEjjXWt4gTT5+GAToPK3e7jYcWmysSfWcd4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Xyr0SRz7vxiMKRAYBIoI3ChRKuowtOfnnbMZJ8zx7u0oYedTH4a/n47S/rZS1/vc9M PT+repf4odj81riRSQ+WNnIPwMxZaAhiKg7ErHf/cHgKQFa6w8ifULR3CYZK3wFeK3Lk 6qFl5x8qkS4HK8TgvlHpeT3saso5xxwU6E1mc= MIME-Version: 1.0 Sender: alpmestan@gmail.com Received: by 10.210.13.17 with SMTP id 17mr3403529ebm.15.1237919401747; Tue, 24 Mar 2009 11:30:01 -0700 (PDT) Date: Tue, 24 Mar 2009 19:30:01 +0100 X-Google-Sender-Auth: 7a5fcfd548813dc5 Message-ID: Subject: Question about the -dlambda option of ocamlc/ocamlopt From: Alp Mestan To: caml-list@yquem.inria.fr Content-Type: multipart/alternative; boundary=0015174c3cca33a5d80465e19209 X-Spam: no; 0.00; -dlambda:01 ocamlc:01 ocamlopt:01 lambda:01 ocaml:01 compiler:01 lambda:01 ocaml:01 compiler:01 blog:98 2009:98 blog:98 2009:98 variables:02 variables:02 --0015174c3cca33a5d80465e19209 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I'm currently studying the lambda code generation phase of the standard OCaml compiler. You can take a look at this for an example : http://blog.mestan.fr/2009/03/22/ocaml-and-dlambda-1/ I'm wondering what is 'makeblock' for ? And why is there '/' after every variable/function name ? Isn't the name sufficient for identifying variables ? Thanks ! -- Alp Mestan --0015174c3cca33a5d80465e19209 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm currently studying the lambda code generation phase of t= he standard OCaml compiler.

You can take a look at this for an examp= le : http= ://blog.mestan.fr/2009/03/22/ocaml-and-dlambda-1/

I'm wondering what is 'makeblock' for ?
And why is there= '/<a number>' after every variable/function name ? Isn't= the name sufficient for identifying variables ?

Thanks !

--
Alp Mestan

--0015174c3cca33a5d80465e19209--