From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA20773; Wed, 13 Jun 2001 11:57:21 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA20868 for caml-list@pauillac.inria.fr; Wed, 13 Jun 2001 11:57:20 +0200 (MET DST) 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 XAA10929 for ; Tue, 12 Jun 2001 23:54:47 +0200 (MET DST) Received: from localhost.localdomain (ppp138.dyn146.pacific.net.au [210.23.146.138]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f5CLshb20618; Tue, 12 Jun 2001 23:54:44 +0200 (MET DST) Received: from ozemail.com.au (IDENT:root@localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.8.7) with ESMTP id HAA11996; Wed, 13 Jun 2001 07:54:42 +1000 Message-ID: <3B268FA2.5330AAC4@ozemail.com.au> Date: Wed, 13 Jun 2001 07:54:42 +1000 From: John Max Skaller X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Pierre Weis CC: Jacques Garrigue , caml-list@inria.fr Subject: Re: [Caml-list] let mutable (was OCaml Speed for Block Convolutions) References: <200106120743.JAA25545@pauillac.inria.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk Pierre Weis wrote: > A more interesting contribution would be to give evidences that > references and arrays and other imperative features are indeed built > with lvalues in Caml. To do that, one must understand what an lvalue is. In C, it is an expression term obeying certain syntactic constraints. That is, it is not a matter of semantics, or typing: an lvalue is a particular piece of syntax. To say that another way, some constraints on the language _syntax_ are not imposed by the grammar, but by additional rules such as 'the argument of the unary & operator must be an lvalue'. This is NOT the case in C++, where the typing is related to lvalueness. Note that in BOTH cases, lvalueness is related to addressability, NOT necessarily mutability. In C++, non-lvalues are definitely mutable! [The rules in C++ are a shambles] -- John (Max) Skaller, mailto:skaller@maxtal.com.au 10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850 checkout Vyper http://Vyper.sourceforge.net download Interscript http://Interscript.sourceforge.net ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr