Using your example with Erik's new C-like language
that was a 'speed test' not an attempt to write code. When one looks at the stopwatch more than the code, things happen. Another lesson that should be taught in school.
When actually producing code I do NOT use these, so my mis-sequencing is basically due to not having sequenced them for years, Had this been actual code it would have been

UCX buf1[48];
UCX buf2[48];
UC index;

for (index = 0; index <48; index++)
{
  buf1[index] = buf2[index];
}

since I did not want to confuse by using 'my' abbreviations I 'hammerd out something that, unfortunately, was wrong (and even more confusing).

In the daily grind, using the above, such do not happen.

sorry for the mistakes

Erik