[OSC_dev] 4 Byte Padding

[Angelo Fraietta]

Adrian Freed wrote:
>>Sos in these instances, the data is being stored in the original OSC
>>message packet similar to storing a struct as a char buffer? So instead
>>of typecasting each data parameter, you are just getting the pointer to it?
> 
> 
> well typecasting involves no copies either. The key is not to move the data if you don't have to and not to realign at great cost to cache performance.
> 
Don't you move it out of the OSC buffer when you receive it as a packet? 
  Or is it already optimised for a 32bit machine from the sender's end?


> 
>>If so, what happens when you go to 64 bit machines?
> 
> 
> Yes, there are now architectures where there is a performance benefit to 64-bit alignment although it will be years before application and OS software catch up to the point where this is an important issue for OSC.

Is there a short code sample where I can see how you get the arguments 
out if you are not just doing a typecast based upon the arguments.  I am 
having difficulty seeing how you are doing it.


-- 
Dr Angelo Fraietta
A.Eng, A.Mus.A, BA(Hons), Ph.D.

PO Box 859
Hamilton NSW 2303

Home Page


http://www.smartcontroller.com.au/

There are those who seek knowledge for the sake of knowledge - that is 
CURIOSITY
There are those who seek knowledge to be known by others - that is VANITY
There are those who seek knowledge in order to serve - that is LOVE
     Bernard of Clairvaux (1090 - 1153)