From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <weis@pauillac.inria.fr>
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by yquem.inria.fr (Postfix) with ESMTP id 8FED9BBBB
	for <caml-list@yquem.inria.fr>; Mon, 23 Jan 2006 10:18:31 +0100 (CET)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id k0N9IV8G023901
	for <caml-list@yquem.inria.fr>; Mon, 23 Jan 2006 10:18:31 +0100
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA11661 for <caml-list@pauillac.inria.fr>; Mon, 23 Jan 2006 10:18:30 +0100 (MET)
Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.202])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id k0N9IU0W012662
	for <caml-list@inria.fr>; Mon, 23 Jan 2006 10:18:30 +0100
Received: by uproxy.gmail.com with SMTP id q2so670944uge
        for <caml-list@inria.fr>; Mon, 23 Jan 2006 01:18:30 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=mx4VQcoydxEOfSi4f216wREV12g6zd6MZQPK2tEfWeRk+xfNo00k322Dqzl/pXc9lwFnL6DSJCBmksxkPa9Mus4Ap7vjhMVMo9P4SAfN6R7k2rVOlC+AVtlcRCwbfIyjxwa9JbJHaYw4VRFTJqqo9C+4+j2WzBRFNup2VAdj9ls=
Received: by 10.49.20.12 with SMTP id x12mr316289nfi;
        Mon, 23 Jan 2006 01:18:29 -0800 (PST)
Received: by 10.49.1.13 with HTTP; Mon, 23 Jan 2006 01:18:29 -0800 (PST)
Message-ID: <6b8a91420601230118s24e945e9j@mail.gmail.com>
Date: Mon, 23 Jan 2006 10:18:29 +0100
From: Remi Vanicat <remi.vanicat@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Pervasives or Printf module ?
In-Reply-To: <dr0cqu$pqh$1@sea.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43D3A058.6030305@yahoo.fr>
	 <200601221534.04835.jon@ffconsultancy.com>
	 <dr0cqu$pqh$1@sea.gmane.org>
X-Miltered: at concorde with ID 43D49F67.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Miltered: at nez-perce with ID 43D49F66.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Spam: no; 0.00; caml-list:01 pervasives:01 printf:01 rewriting:01 coq:01 rewriting:01 wrote:01 rewrite:01 remi:01 remi:01 vanicat:02 vanicat:02 renaming:02 module:03 latter:03 
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled 
	version=3.0.3

2006/1/22, Vincenzo Ciancia <vincenzo_yahoo_addressguard-gmane@yahoo.it>:
> Jon Harrop wrote:
>
> > To get the latter to act as the former
> > does, you must beta expand (I think that is the correct technical term)
>
> In computer science literature, alpha conversion is usually the renaming =
of
> a bound variable (fun x -> T =3D fun y -> T[y/x] provided that y does not
> occurr in T), beta _reduction_ is function application ((fun x -> T)(T') =
=3D
> T[T'/x]) , and _eta_ expansion is the term rewriting you're looking for.
>
> I don't know why, maybe it's just the order in which they were enumerated
> originarily, but where are gamma, delta, epsilon, zeta rewrite rules? :)

In the coq manual, one can see severall other rewriting rule, like
iota-reduction, delta-reduction and zeta-reduction.