I was mostly referring to DGD's terms for them. I leave implementation defined the terms used by a mudlib running on top of it. It's entirely possible that the "efun" label is used for backward compatibility, or as an abstraction around afuns which are a DGD term the klib may well have sought to hide.