RE: [GD-General] Scripting

[Brian H. <bri...@py...>]

> this is how we're implementing things - we are using the 
> scripting language in the very way that brian and others have 
> been trying to avoid - as a complete language with the 
> requisite 'language constructs', switch statements, etc...

Okay, to avoid muddling semantics, there's "the language" and there's
"how it's used".  It's entirely possible to use Python as an extension
language call by an app, as an application language that calls an
engine, or somewhere in between.  I use Lua, ostensibly a scripting
language, for data definitions.  I wouldn't call it a scripting language
in my case though.

My instinct is that a scripting language as an "extension" (vs. "as
data") seems ill advised at times, because you kind of have
responsibilities that are mixed and often poorly defined.  Using it as
your primary application language means it's no longer "scripting", it's
just the language you happen to be developing in and you're now calling
into a separate native engine for system specific tasks.  That seems
completely reasonable if you feel the language itself is much more
productive than C or C++ or whatever.

Brian