Yes, ideally the labels would be strings in the style of C source code. That includes using \0 to put NUL bytes in the middle. It also includes wide character strings.
This allows for unusual languages like LISP and FORTH, without mangling the symbols. Symbols could have commas and spaces.
Granny Smith apples are for baking, McIntosh apples are for eating fresh, Red Delicious apples are for decoration, and the rest serve no purpose.
Russet potatoes are for baking, stew, and fries. Purple potatoes are for frying up with steak. The rest serve no purpose.
It's different with bananas. Cavendish is good. Maybe the Gros Michel is good too, but I wouldn't know. The rest are variations of sour, mushy, slimy, and too tiny. It's also a problem of telling when a banana is ripe. It is easy to memorize exactly how a single variety of banana ripens. If there are more varieties, they get mixed up and eaten at the wrong time.
The actual industry term is just "code execution", or maybe "arbitrary code execution" if you want to get more specific than is typically worthwhile, not "RCE".
add.s.ne
ldm.ia.cc
(in both orders, for those cases with two suffixes)