I will change to LiteC, I already have the free version on my pc and played around a bit with it.
However I have a project to do in c-script and thus not enough time for jumping on the LiteC train

Whoa... I'm almost sorry I started something.

So, being a relatively good programmer, I should learn Lite-C? What if I get to a professional level, and experience the problem that Tompo outlined? Could I write C++ or Lua plug-ins to connect with Lite-C code?

Quote:

---

with included instructions/syntax (like in c-script) that hook into the engine and are especially made for game features.

---

With Lua or C++, you could create code that works specifically for gameing. But someone said that certain functions were specific to the engine. Could those [certain functions] be locally altered in code?

Finally, What is the advantage of the payed-for version of Lite-C vs. the free version? How are they different?

How might a user create a memory leak in Lite-C?

If one keeps programming "c-script style", lite-c will not result in more risks, and will not have many advantages. The fact that it is now possible for newbies to write bad code might result in problems. But I don't see this becomming a big problem. The fact that c-script is proven and stable is a big advantage, though. Nevertheless, I am a big supporter of lite-c.

However, these risks are not really a new thing. You could create memory leaks in C-script (and infact I've seen many people create them, even experienced developers). For example:
function myfunction()
{
myStringPointer = str_create("hello world");
error(myStringPointer);
}
is a memory leak, unless myStringPointer is used to str_remove() the created string.

A new way to create memory leaks in lite-c:
MyStruct* myStruct;
myStruct = malloc(sizeof(MyStruct));
... and not freeing the memory

I'm starting to get that "Sht, I'm screwed" feeling...

...Switching over to Lite-C

Damn, I'm a noob again

If someone makes good Lua bindings for A6 I would definitely pay a good price for it.