This is a first step in hiding vtable functions - not only: Using these macros also provides more readable source files:
While just talking about vtable functions:
- we currently have 259
- 140 of these are some _keyed variants only get/set_{type}_keyed and defined/exists_keyed are supported by opcodes [1]
- 21 methods are xx_same variants (e.g. bitwise_or_same), which are not called from anywhere
IMHO vtable.tbl (and default.pmc) need major cleanup.
[1] I think I did already clearly outline, why they can't have distinct opcodes.
leo
