From: Chris Hecker <checker@d6.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] bigarrays and toplevel on Win32?
Date: Mon, 05 Mar 2001 09:37:36 -0800 [thread overview]
Message-ID: <4.3.2.7.2.20010305091601.036cdef0@shell16.ba.best.com> (raw)
In-Reply-To: <20010305175715.B16895@pauillac.inria.fr>
>This is a known bug in OCaml 3.00. A simple fix is described here:
> http://caml.inria.fr/bin/caml-bugs/fixed?id=94
>and of course this will be fixed in OCaml 3.01.
Ack, sorry, the one place I didn't look was the bug list. Sorry to waste your time.
>The party line on unsafe array accesses is unclear: on the one hand,
>we do not want to encourage their use, as it can break type safety and
>dramatically reduce the safety of the programs; on the other hand,
>they are handy when benchmarking against C or Fortran :-)
I'd like to have the choice. I prefer unsafe_get/unsafe_set to -unsafe because it lets me choose where to be risky.
It doesn't actually look like it would be too hard for me to make -unsafe work in the source (adding the unsafe_(set|get) would be harder, it seems). Couldn't I just have ccmgen.ml's bigarray_indexing function not generate Ccheckbound ops if Clflags.fast is set?
>I'll keep that in mind for 3.02.
Cool. Is there an autmated or semi-automated way to do these primitive additions, or do you manually do it?
Chris
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-03-05 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 7:43 Chris Hecker
2001-03-05 16:57 ` Xavier Leroy
2001-03-05 17:37 ` Chris Hecker [this message]
2001-03-06 17:18 ` Brian Rogoff
2001-03-05 20:52 ` Bruce Hoult
2001-03-05 21:28 ` John Prevost
2001-03-07 16:00 ` Dan Grossman
2001-03-07 21:04 ` John Prevost
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=4.3.2.7.2.20010305091601.036cdef0@shell16.ba.best.com \
--to=checker@d6.com \
--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).