>>
>>In fact, this behaves exactly as documented. The table/cursor is not hurt, it is zapped, a completely acceptable operation. The cursor is not left nonoperational, as the instruction that follows the macro proves.
>
>It does, but that does not make it less confusing.

It may be confusing if we don't read the documentation, but then again, none of us would start to program for a living before reading the language documentation, wouldn't we?