caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: jarvarvar@airtel.net
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Using 16 bits integers
Date: Tue, 3 Jul 2001 11:21:58 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.21.0107031115210.15984-100000@shell5.ba.best.com> (raw)
In-Reply-To: <23ae62237bc3.237bc323ae62@airtel.net>

>From the manual section on Bigarray:

Big arrays can only contain integers and floating-point numbers, while
Caml arrays can contain arbitrary Caml data types. However, big arrays
provide more space-efficient storage of integer and floating-point
elements, in particular because they support ``small'' types such as
single-precision floats and 8 and 16-bit integers, in addition to the
standard Caml types of double-precision floats and 32 and 64-bit integers. 

...

type int16_signed_elt
type int16_unsigned_elt

It's an interesting question in general as to what should be the basic
types of the language, should we have modular types, unicode characters, 
etc. I have similar issues in that a standard file format that I use a lot
specifies 32 bit integers and if I want to follow that exactly I need to
use the less performant int32 rather than the 31 bit int on 32 bit 
machines. Fortunately, that problem will be lessened when we enter the 
64 bit world. 

BTW, if you still find the need to go to C, you can use the Bigarray code 
as a template to start from so that you can link your C into OCaml.

-- Brian

On Tue, 3 Jul 2001 jarvarvar@airtel.net wrote:

> Hello, I'm just new to OCaml. I'm writing a program wich uses a lot of
> 16 bits operations, and writes them to a buffer. For writing into the
> buffer, it is needed for the data to be in 16 bits, not in 32 bits.
> Exactly, the program is like a sound synthesizer, so data cannot be send
> to sound card in 32 bits.
> My problem with OCaml is: how can I manage 16 bits data, and make
> operations with it? I had not seen any type in Ocaml with 16bits lenght
> (int is 32 bits in my machine). This will frustate my project if I do
> not find a solution, so I will use C if there is no other solution...
> but I would not like to do if I can avoid it, because I like very much
> Ocaml.
> 
> I'm hopping your answers. Thanks.
> 
> -------------------
> Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
> 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/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-07-03 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 18:05 jarvarvar
2001-07-03 18:21 ` Brian Rogoff [this message]
2001-07-03 18:34 ` David McClain
2001-07-04  2:21 Arturo Borquez

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=Pine.BSF.4.21.0107031115210.15984-100000@shell5.ba.best.com \
    --to=bpr@best.com \
    --cc=caml-list@inria.fr \
    --cc=jarvarvar@airtel.net \
    /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).