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