Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Python support

<< < (2/2)

Michael:

--- Quote from: sethjackson on January 14, 2006, 03:13:52 am ---Yeah I agree. Next question..... How do you add support for a new language?

--- End quote ---

I think that this C::B wiki article and this topic could be of some help.

Michael

thomas:

--- Quote from: Takeshi Miya on January 13, 2006, 11:33:24 pm ---However, I think we should encourage people (maybe writting in the bounties forum) to add support for other languages.
--- End quote ---
I don't think so. The "Bounties" forum is for things we absolutely need, and yet another scripting language is no such thing.
First, the actual need for scripting is over-estimated (we have a working implementation for 4 months now, and nobody uses it).
Second, the Angelscript engine has a lot of advantages over Perl, Python, or whatever other script language we could use (to name just a few of many: security, ease of use, integration, speed, lack of external dependencies).


--- Quote from: mosfet on January 14, 2006, 02:07:01 pm ---Basically you call the interpreter (instead of the compiler) with a list of file.
--- End quote ---
How can that be used, for example, to add files to a project, to insert text into the editor, or to start a build process? I agree that it is really simple to run a script in an external interpreter, but integrating it into the IDE is a wholly different matter.

Urxae:
There seems to be some confusion here about what kind of support was requested: support for scripting C::B itself, or support for editing, "compiling" and running programs written in scripting languages from C::B.
I'm guessing the OP meant one or the other, not both. In the light of his second post I'd assume the latter, but I'm not entirely sure.

takeshimiya:

--- Quote from: Urxae on January 15, 2006, 01:06:17 am ---There seems to be some confusion here about what kind of support was requested: support for scripting C::B itself, or support for editing, "compiling" and running programs written in scripting languages from C::B.
I'm guessing the OP meant one or the other, not both. In the light of his second post I'd assume the latter, but I'm not entirely sure.

--- End quote ---
Of course I'm referring to support for "editing" and "compiling" and "running" programs, and I think mosfet was talking about that.

Not for scripting C::B itself, in which AngelScript fits perfectly. Perhaps the reason nobody is using that yet, is that C::B doesn't provide examples at least of using AngelScript in it.

But I repeat, here we're talking about supporting more languages in the IDE, not for scripting C::B itself.

thomas:
Oh...
Well, if that is all you want, then it is quite trivial, really. You could just run the interpreter as a tool, and use the current editor variable, for example. That needs (almost) zero setup.

Or you might just do like you were adding a new compiler, as pointed out by Michael. Should not take more than a few minutes.

I discourage going for a more complicated solution (a dedicated compiler/interpreter plugin), since very likely that would result in a lot of your work becoming obsolete in a couple of weeks.

Navigation

[0] Message Index

[*] Previous page