Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
To: Jaroslav Kysela <perex@perex.cz>, Paul Davis <pbd@Op.Net>,
	alsa-devel@lists.sourceforge.net
Subject: About integer64
Date: Thu, 09 May 2002 10:10:10 +0200	[thread overview]
Message-ID: <3CDA2EE2.A3C6D824@alsa-project.org> (raw)


I don't think that's a bad thing to have support for 64 bit integers
(perhaps for future use, who knows), but I think that to use this to
store a fixed point float is a big mistake.

If you think for it you realize that it's *not* an integer and
applications are betrayed in their expectation.

I see two possible solutions:
1) convert internal representation to float (or double) and add support
for this type of data
2) use SNDRV_CTL_ELEM_TYPE_BYTES

As I've already said I prefer 1) but too 2) is far better that to have a
wrong use of a data type.

-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

             reply	other threads:[~2002-05-09  8:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  8:10 Abramo Bagnara [this message]
2002-05-09 10:37 ` About integer64 Jaroslav Kysela
2002-05-09 11:07 ` Paul Davis
2002-05-09 12:32   ` Abramo Bagnara
2002-05-09 12:57     ` Paul Davis
     [not found] <200205091107.NAA14247@gate.perex.cz>
2002-05-09 11:18 ` Jaroslav Kysela
2002-05-09 12:27   ` Abramo Bagnara
2002-05-09 12:59     ` Paul Davis

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=3CDA2EE2.A3C6D824@alsa-project.org \
    --to=abramo@alsa-project.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@Op.Net \
    --cc=perex@perex.cz \
    /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