Kornalius,
Hi. I'm not an accomplished C coder. I used to use OnboardC for Palmos when I had one - I loved it. It would generate a skeleton event structure and you just plugged bits of code in where you wanted them. There was an Onboard gui form builder and resource compiler. It was so simple to use... Those were the days.
The point is, it produced apps which were fast. They were about 10% faster than equivelant code generated by gcc. To me speed of processing is one of the top bullet points you advertise about a language. Why? Cos its what the end user and therefore the programmer wants and it ultimately gives you more scope, more choice, more excellence.
I can see what mervjoyce and pointoflight are saying: What good is an unreliable Hare in a race? Give me a Rabbit that gets past the finish line.
Your dynamic compiling method seems like an inspired choice. I don't pretend to know how it works but if it was me, and all things being equal, I don't think I'd abandon the idea too quickly. Could you keep it as a feature only to be used on code where it doesn't cause any bizarre problems?
How does the dynamic compilation work? Maybe talking it through with the guys on here would help identify the problem.
Hope this helps.
Kind regards,
Andy