From: "David McClain" <dmcclain1@mindspring.com>
To: "caml" <caml-list@inria.fr>
Subject: [Caml-list] BigArray's Implementation
Date: Sat, 31 Jul 2004 11:15:35 -0700 [thread overview]
Message-ID: <001b01c4772a$636aec60$0201a8c0@dylan> (raw)
Why is it necessary to do so much of the BigArray management in C? You have
a perfectly good language for assuring that things go correctly, in OCaml. I
see no declaration of BigArray structure in the OCaml Library code (the ML
part), and huge reliance on C subroutines for mundane things like array
bounds checking, accessing dimensions, and so on. The only part that seems
reasonable as a candidate for C code is the underlying Get and Set with
mutation of representation, e.g., single-float to OCaml double-float
representation and back...
David McClain
Senior Corporate Scientist
Avisere, Inc.
+1.520.390.7738 (USA)
david.mcclain@avisere.com
-------------------
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
reply other threads:[~2004-07-31 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001b01c4772a$636aec60$0201a8c0@dylan' \
--to=dmcclain1@mindspring.com \
--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).