Differentiating engine and user functions

[sunarch]

I did not want to PR this until I get your opinion:

I believe it would be useful to differentiate the source of Lua functions with a prefix:

• Functions exposed from scripts.c could be e for engine or k for KIAVC, e.g. eShowObject.
  • Some of them already have a kiavc prefix, e.g. kiavcRequire and logging.
• Functions from scripts in the lua/engine folder could be c for collection or e if not taken above.
  • I think engine could be misleading here, so e above and c for this, which is better also in that they are both one-high letters, unlike k.

[lminiero]

Mh I'm not a big fan of the idea, to be honest: it may cause the name of functions to quickly explode in length. I'm not sure I understand the reference to collections, though?

[sunarch]

That's why I was only suggesting one letter, so that it doesn't make it much longer. But I understand you skepticism. It's only an idea, anyway.

"Collection" is just a possibility I came up with for the scripts in the lua/engine folder. I already used e for the functions exposed by the C engine code, so that's why I needed something else.

But it works the other way too: cFunction for functions exposed by the C code, and eFunction for functions in Lua that are shipped with the engine.