No it wouldn't. I am not suggesting changing the current way byte offsets are used, but adding a new one with a different set of conventions or methods.
As to your other question, simple. Something like: MymemoryBlockVar.myStructType[3].element1 Could be used to get the fourth structure on the memory block ( containing an array of structures of type myStructType ) and then address an element in that structure - element1. The use of [ ] style parentheses would indicate that the offset is being determine NOT by BYTE but by taking into account the size of the datatype. So for example one could do: myInt32Arraymemoryblock.Int32[3] = 4 This would set the fourth integer in an array of ints referenced in the memory block. This sort of addressing is particularly useful in Declares dealing with audio processing, since it is standard to pass audio data by pointers to blocks containing C arrays of integer or float values representing samples. ( In addition pointers to pointers to floats are also often passed , they could then be dereferenced and handled in the way stated above ) The.5 index issue would simply not arise. On 14/9/06 15:15, "Mike Woodworth" <[EMAIL PROTECTED]> wrote: > > the only objection in my mind is it would break tens of thousands of > lines of my code across lots of projects. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
