Originally Posted by radnomguywfq3
I wrote a scripting engine once but it was a bit of a mess because I skipped the intermediate level of compilation.
With .Net you can just compile C# code on the fly that runs equally as a fast as the code which compiled it, compile times for .Net are incredibly fast as well (because it only has to compile to CLI.) The .Net framework virtually ships with a scripting engine - at least reflection makes it seem like such. That's one of the reasons it's so powerful.
So while I encourage what you're doing, I would do it w\ a language that doesn't rely on a framework that carries around a compiler where-ever it goes (if you aren't already.)
Another idea is to write it so that it supports the compact .net framework, because that framework doesn't support reflection as well or on the fly compiling.
But for my engine, I have a 'scripts' precompiled to assemblies. So that it would be compiled directly into CLI - so runtime analysis & compilation wasn't required.
With .Net you can just compile C# code on the fly that runs equally as a fast as the code which compiled it, compile times for .Net are incredibly fast as well (because it only has to compile to CLI.) The .Net framework virtually ships with a scripting engine - at least reflection makes it seem like such. That's one of the reasons it's so powerful.
So while I encourage what you're doing, I would do it w\ a language that doesn't rely on a framework that carries around a compiler where-ever it goes (if you aren't already.)
Another idea is to write it so that it supports the compact .net framework, because that framework doesn't support reflection as well or on the fly compiling.
But for my engine, I have a 'scripts' precompiled to assemblies. So that it would be compiled directly into CLI - so runtime analysis & compilation wasn't required.
---Thanks everyone for support
Jason: You still mad nigga.
<3 Originally Posted by NextGen1
Whats your plan on releases?
