[gmpi] Re: Topic 3: Cross platform

[...]
> I have a sugestion that we use a naming system where the bit size is
> appended to the type. I cant remember where i got this from but it avoids
> any ambiguity with differant type names in diferant languages. You just
> typedef these in the SDK.
>
> int8, int16, int32, int64
>
> uint8, uint16, uint32, uint64

I think typedefs like these are in C99 and we should probably
use those.

> float32, float64, float80

These don't make much sense. Just use float/double.

> bool8, bool16, bool32,

C99 already has a boolean typedef IIRC. I fail to see the use of
more than one boolean type...

> i also think it should be explicitly defined what true and false are in
> regard to booleans because some languages true and false are 0 and 1, and
in
> others they are ==0 and <>0. This would probably be better aligned with
the
> C standard? For example in Delphi the default boolean is 0 and 1 so
anything
> <> 1 is false.

Why is this necessary? Also "true" and "false" are C++ keywords and
should not be used.

--ms




----------------------------------------------------------------------
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: