Re: AU version hex format
Re: AU version hex format
- Subject: Re: AU version hex format
- From: William Stewart <email@hidden>
- Date: Fri, 10 Oct 2003 12:55:37 -0700
We're using straight Hex: Thus 2.3.1 would be:
0x20301
The Validation tool will try to print out the version in this format -
and checks that the number returned from the component resource is the
same as the number returned from the GetComponentVersion API call (but
it doesn't do any pass/fail logic on the format of these numbers)
Bill
On 09/10/2003, at 11:49 PM, Jim Wintermyre wrote:
Reviewing some earlier discussion on this, I came across the following
response from Bill to Marc:
> I was wondering, is it explained anywhere what exactly the format
for
> Audio Unit version values should be? I mean the value in the
'thng'
> resource and returned by the Version component selector. For some
> reason,
> I was under the impression that the format was like this:
>
> 0xMMMMmmbb
This is the format that we are using
I have a question. Is this similar to the old 'vers' format where the
M/m/b numbers are actually in *BCD*? Should our component version
numbers be BCD or straight hex?
Thanks,
Jim
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.