caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Thomas Fischbacher <tf@functionality.de>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] Bigarray question
Date: Wed, 19 Dec 2007 19:15:47 +0000	[thread overview]
Message-ID: <47696DE3.4090302@functionality.de> (raw)
In-Reply-To: <47695924.8090202@inria.fr>


Xavier,

>>as far as I can tell, it is easy (but not explicitly allowed in the
>>documentation) to allocate a Caml bigarray and change the data
>>pointer inside that bigarray afterwards.
>>There is no problem in implementing this, technically speaking.
>>But this would require a change to the ML documentation stating
>>that it is explicitly considered as permissible to change the
>>data pointer in a bigarray. Can I get that, please?
> 
> I see no reason why this would cause problems, as long as the data
> pointer points to C data of the right shape and dimensions.  (Of
> course, you could update the dimensions of the bigarray as
> appropriate, if needed.)  I don't think I would document this, as I
> wouldn't quite know how to word it in the docs, but you have my
> encouragements to try and report problems if any.

Just adding a line to the documentation which states that
"it is permitted to dynamically change the data and dims
fields of the bigarray data structure from within C" would be
sufficient.

-- 
best regards,
Thomas Fischbacher
t.fischbacher@soton.ac.uk


  reply	other threads:[~2007-12-19 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 17:44 Thomas Fischbacher
2007-12-19 17:47 ` [Caml-list] " Xavier Leroy
2007-12-19 19:15   ` Thomas Fischbacher [this message]
2008-01-28 12:57   ` Thomas Fischbacher
  -- strict thread matches above, loose matches on Subject: below --
2005-11-25 18:19 Thomas Fischbacher
2005-11-25 20:06 ` [Caml-list] " Dmitry Bely
2005-11-27 22:48   ` Thomas Fischbacher
2005-11-28  9:39     ` Dmitry Bely
2005-11-28 21:30       ` Thomas Fischbacher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47696DE3.4090302@functionality.de \
    --to=tf@functionality.de \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).