From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 497267EE51 for ; Sun, 26 May 2013 00:57:21 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=pra; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=mailfrom; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@einhorn.in-berlin.de) identity=helo; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="postmaster@einhorn.in-berlin.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnQBALtAoVHAbSoIlGdsb2JhbABahnO5VYUngQgWDgEBAQEJCwkJFAQkgiMBAQUjBFIQCwkPAgIFIQICDwUYMS6HcgSrEJEEFoEQjXcHgkEyYQOPB4gzlFKBZiQ X-IPAS-Result: AnQBALtAoVHAbSoIlGdsb2JhbABahnO5VYUngQgWDgEBAQEJCwkJFAQkgiMBAQUjBFIQCwkPAgIFIQICDwUYMS6HcgSrEJEEFoEQjXcHgkEyYQOPB4gzlFKBZiQ X-IronPort-AV: E=Sophos;i="4.87,742,1363129200"; d="scan'208";a="18981163" Received: from einhorn.in-berlin.de ([192.109.42.8]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 May 2013 00:57:20 +0200 X-Envelope-From: oliver@first.in-berlin.de Received: from first (e178019102.adsl.alicedsl.de [85.178.19.102]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id r4PMvJjZ002929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 26 May 2013 00:57:19 +0200 Received: by first (Postfix, from userid 1000) id 66C9E154066B; Sun, 26 May 2013 00:57:19 +0200 (CEST) Date: Sun, 26 May 2013 00:57:19 +0200 From: oliver To: Gabriel Scherer Cc: Wojciech Meyer , Siraaj Khandkar , Arnaud Spiwack , OCaML Mailing List Message-ID: <20130525225719.GC1958@siouxsie> References: <20130523235355.GI6510@siouxsie> <20130524233015.GE1923@siouxsie> <37A1A2D3-5993-4675-9937-ED3965793D1D@khandkar.net> <20130525004045.GH1923@siouxsie> <20130525110457.GA1947@siouxsie> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Subject: Re: [Caml-list] OCaml's variables On Sat, May 25, 2013 at 01:49:46PM +0200, Gabriel Scherer wrote: > The name "variable" has been used for centuries by the mathematicians > to denote exactly names that refer to values (of course immutable > values, we're talking about mathematical objects her). There is no > point in trying to change it because some people conflate this notion > with mutability. [...] Yes, after rethinking this, this seems valid to me. Even in a function that has only one solution, the variables are called "variables". I had in mind: if there is only one fixed solution, it is not variable, hence it can't be called a variable. With f(x) = 3 * x + 2 "x" is the variable. f(x) can be calculated out of the function and the valaue of x. Infinit many results, because infinite many x-values => variable. But for f(x) = 0, which means 0 = 3 * x + 2 the "x" also is called a variable, even though there is only one solution. (...and "one solution" means: fixed result, not variable; but the term "variable" will be used nevertheless. So, you are right. I just was on the wrong track. Temporarily black out ;-) [...] > The name "variable" is also used in the expression "type variable", > which denotes for example the 'a in > val id : 'a -> 'a > and which is clearly not associated to any form of mutation. I wonder why I never had a problem with "type variable" but was very picky about the term variable at the mentioned refman-page. But I think it was influenced by the situation of the above mentioned problem: "if it has only one fixed value it is not varible, it's fixed". But as also explained above, the "x" nevertheless is called variable. So my mouring about the reference manual at that point was rubbish. Ciao, Oliver P.S.: Thanks for the patience/calmness of you and the others.