From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: [Caml-list] Bigarray is a pig
Date: Fri, 23 Jul 2004 13:36:08 -0700 [thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDIEIOHFAB.vanevery@indiegamedesign.com> (raw)
I have been looking at the sources of the Bigarray implementation. I am
chagrined to discover that not only does Bigarray cost a function call
per array element access, but a number of additional piggish things
happen per access. To C/C++ programmers interested in performance, this
defeats the purpose of using unboxed array elements. If I wanted to pay
function call overhead per element, for instance when communicating with
OpenGL, I'd simply call functions.
I am wondering if there is some way to present a block of C memory to
OCaml, and then have OCaml use it directly? If so, I could envision
writing up something I'd call 'Fastarray'. But I'm interested in any
pitfalls you might see, such as range check requirements.
In other news, I've been trying and trying to announce the next ML
S*attle meeting on Tuesday, July 27th. E-mail me for details. These
anti-spam filters are maddening.
Cheers, www.indiegamedesign.com
Brand*n Van Every S*attle, WA
Praise Be to the caml-list Bayesian filter! It blesseth
my postings, it is evil crap! evil crap! evil crap!
-------------------
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
next reply other threads:[~2004-07-23 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 20:36 Brandon J. Van Every [this message]
2004-07-23 21:05 ` Brian Hurt
2004-07-24 9:49 ` Brandon J. Van Every
2004-07-23 21:05 ` Olivier Andrieu
2004-07-24 9:07 ` Brandon J. Van Every
2004-07-24 9:59 ` Marcin 'Qrczak' Kowalczyk
2004-07-25 9:09 ` David McClain
2004-07-24 10:39 ` Markus Mottl
2004-07-23 21:45 ` David McClain
2004-07-23 22:01 ` David McClain
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=OOEALCJCKEBJBIJHCNJDIEIOHFAB.vanevery@indiegamedesign.com \
--to=vanevery@indiegamedesign.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