[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2005-11-27 (22:48) |
From: | Thomas Fischbacher <Thomas.Fischbacher@P...> |
Subject: | Re: [Caml-list] Bigarray question |
On Fri, 25 Nov 2005, Dmitry Bely wrote: > Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE> writes: > > > As far as I can see from the documentation, it is not explicitly permitted > > to change a once allocated bigarray data structure in such a way that one > > replaces the data pointer by some other data pointer (while retaining > > size and type). This would, however, be quite useful in some situations. > > Is your bigarray a wrapper around some externally allocated data, created > via alloc_bigarray() C call? It's a somewhat special case of just that situation, yes. I supposed I may just do so, however, the specification (documentation) does not give me any guarantee that this is valid, so, at least the documentation has to be changed before I can rely on this. There is a subtle difference between "just accidentally works" and "works because it is guaranteed by specification". -- regards, tf@cip.physik.uni-muenchen.de (o_ Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //\ (lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_ (if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)