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 NAA11084; Sat, 8 Jun 2002 13:19:01 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f 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 NAA11192 for ; Sat, 8 Jun 2002 13:19:00 +0200 (MET DST) Received: from mailg.telia.com (mailg.telia.com [194.22.194.26]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id g58BIxn20298 for ; Sat, 8 Jun 2002 13:18:59 +0200 (MET DST) Received: from d1o903.telia.com (d1o903.telia.com [195.252.34.241]) by mailg.telia.com (8.11.6/8.11.6) with ESMTP id g58BIx421015; Sat, 8 Jun 2002 13:18:59 +0200 (CEST) Received: from [212.181.190.19] (t5o903p19.telia.com [212.181.190.19]) by d1o903.telia.com (8.8.8/8.8.8) with ESMTP id NAA24387; Sat, 8 Jun 2002 13:18:57 +0200 (CEST) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Sat, 08 Jun 2002 13:23:18 +0200 Subject: Re: [Caml-list] look operator From: Winfried Dreckmann To: Michel Quercia CC: =?ISO-8859-1?B?gA==?= caml list Message-ID: In-Reply-To: <20020607155250.7b75fdef.michel.quercia@prepas.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk on 07.06.2002 15:52 Uhr, Michel Quercia at michel.quercia@prepas.org wrote: > Well, I can easily add such a function, but there remains a few problems > to solve first. > > 1. Is it okay to have some matrix entry change of value at any time > because we are reusing the tref for some other computation ? Some > machinery could be used to prevent this, for instance clearing the tref > once its value has been "transfered" through a "set" operation. > 2. We would need a lot of different "set" functions, one for vectors, one > for matrices, one for each (record type, mutable field) pair that may > happen to be usefull... > > 3. We can restrict the spread of mutable data to vectors and provide a new > datatype : tvector with its collection of associated functions : vlook, > vadd_in, vmul_in, ... > > My preference goes to 3. I thought of something like 1, but you are right, 3 would be the most practical way. > Regards, Winfried Dreckmann ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners