[gmpi] Re: Decision Time: 8.3
- From: "Koen Tanghe" <koen@xxxxxxxxxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Tue, 16 Sep 2003 02:31:02 +0200
----- Original Message -----
From: "Mike Berry" <mberry@xxxxxxxxx>
> - The precision problem that I indicated.
> - The rounding issues, which are numerous, from mismatched rounding
> functions to slow float->int conversions.
Yes, I tend to agree.
And anyway, I think that values that are meant to be represented as discrete
values should be represented as such (the same holds for bool), especially
if we want to allow for generic UI's, but also for the user's convenience.
I'm not saying that we should take into account all possible data types, but
the ones that have been mentioned are very basic and widely used:
- double (for high precision)
- float
- signed integer
- unsigned integer (same as enum, no?)
- bool
- string
- general blob (with a header containing blob type ID, version and length?)
I could live with a single real (probably double given the mentioned issues)
on these conditions:
- exact representation of the above mentioned types is possible (no loss of
information)
- there are predefined functions that take care of the conversions for me on
each platform and in an efficient way
But I'd rather see the thinks implemented in the terms I'm thinking about
them, not as disguised forms of them...
Just my thoughts.
Koen
----------------------------------------------------------------------
Generalized Music Plugin Interface (GMPI) public discussion list
Participation in this list is contingent upon your abiding by the
following rules: Please stay on topic. You are responsible for your own
words. Please respect your fellow subscribers. Please do not
redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
Other related posts:
