caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Wish List for Large Mutable Objects
Date: Sun, 1 Aug 2004 20:20:38 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDOEPNHFAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <002101c47839$c9c55bc0$0201a8c0@dylan>

David McClain wrote:
>
> I have a perfectly good running VM as user process library
> running right now
> in C++ that allows for mixed array files, arbitrary offsets
> into the file
> for various array pointers, and this is all transparent to
> the user just as I indicated in my wish list for OCaml.

But it doesn't do scatter-gather DMA.  A user process only grants so
much control, and you seem to want an awful lot of control.  Hence my
suggestion that you tweak an OS.

> In more than 20 years of scientific data access and analysis
> I have only
> seen uniform arrays, one per file, generated by neophytes. In
> just about
> every case I can remember; NetCDF, HDF, FITS, RIF Wave Files,
> MPEG, etc., these are all compound object files.

Us neophytes call them 'file formats'.  They aren't arrays.  I think
we'll be at loggerheads until we agree what an 'array' is.

> The trouble with the simple minded
> approach of one array per file is that most data acquisitions
> will then end
> up with dozens of component data files and it becomes a
> tracking nightmare
> to keep them all coordinated. Not so if you permit compound
> document files.

What does this have to do with Bigarray?  Bigarray provides uniform
basic types in unboxed consecutive memory locations, ala C or Fortran.
That's the entire point, to communicate with arrays as C and Fortran do
them.  Why are you expecting it to be something exceedingly different?

> With a language as rich and wonderful as OCaml, I really
> can't understand your hostility

I haven't spoken with hostility.  I gather you're somewhat attached to
your problems, to view my comments as hostility.

> to useful additions to the language.

Clearly, you think your ideas are useful to you.  Whether others think
they're useful to them, remains to be seen.

> If you don't want to
> play, you don't have to join my sandbox -- find another.

You've lost me here.  Are you saying that if you hear feedback you don't
like, that those giving the feedback should leave caml-list or just be
quiet?


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!  Bigarray!
Unboxed overhead group!  Wondering!  chant chant chant...


-------------------
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-08-02  3:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 18:29 David McClain
2004-08-01  3:36 ` Brandon J. Van Every
2004-08-02  5:28   ` Brandon J. Van Every
2004-08-01  4:06 ` Brandon J. Van Every
2004-08-02  2:38   ` David McClain
2004-08-02  3:20     ` Brandon J. Van Every [this message]
2004-08-02  3:32       ` David McClain
2004-08-02  5:14         ` Brandon J. Van Every
2004-08-02  8:00           ` Ville-Pertti Keinonen
2004-08-02  9:12             ` David McClain
2004-08-04  7:24     ` Alex Baretta

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=OOEALCJCKEBJBIJHCNJDOEPNHFAB.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;
as well as URLs for NNTP newsgroup(s).