General information
Category:
Coding, syntax & commands
>update: and for Mem4UToNum ?
I'ld hesitate, since somebody could read that as a "MemoryForYouToNum" <g>.
I was thinking more about MemU32ToNum:
Seen from pure hardware, MemU4ToNum seems to be the shortest and also safe for future developments. On the OS level there are sometimes operations/pointers 32 <= x <= 64, which AFAIK not always fall on a byte border, but these tend to *stay* pointers, so no need to transform.
regards
thomas
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only