> > Who says you can only have one scripting language? Put in a > > couple and let people use whichever they prefer. This get's hairy very quickly. you have to worry about marshalling in and out of the various interpreters. It's not too bad until you start to implement *extensions* in the scripting languages, where you'd end up with one language calling another... a pain.
- Re: Our first potential flame war: which scripting lang... Shannon Wells
- Our first potential flame war: which scripting lan... Gavin Thomas Nicol
- Our first potential flame war: which scripting lan... Ed Peschko
- Re: Our first potential flame war: which scripting... Robert Sievers
