Actually, the examples are correct. The context for this particular snippet is memory-mapped IO, so the `to` pointer is actually the memory address where some external device is mapped to and accepting input. Repeatedly writing to that location causes the values to be sent to the device.
OK, thanks for the explanation.
This is a perfect example of why comments that explain why something is going on, rather than just what is going on, are so useful!
I think in this case you could just put the write into a function/macro that documents it's intent.
It already is - the function is called "send", and rather than wasting its time just doing one write, it does a whole pile of them at once ;)
There are many good reasons for making functions, and occasionally even a good reason to write a macro, but avoiding writing a comment is not one of them.
I disagree. Writing a comment to express something that can adequately be expressed by code adds overhead to reading it.
That looks to me like a made-up problem. I could be persuaded otherwise, though, so post some code that shows how it works for this particular case.