GSoC More AI interfaces: Difference between revisions
From Spring
Jump to navigationJump to search
Brain damage (talk | contribs) New page: = GSoC idea: Limited play area = == Why == To attract more AI developers who prefer languages which don't currently have bindings for. == Background == The Spring engine's AI interface s... |
|||
| Line 2: | Line 2: | ||
== Why == | == Why == | ||
To attract | To attract AI developers who prefer languages that currently don't have bindings. | ||
== Background == | == Background == | ||
Revision as of 22:51, 11 March 2010
GSoC idea: Limited play area
Why
To attract AI developers who prefer languages that currently don't have bindings.
Background
The Spring engine's AI interface supports bindings for multiple languages, currently legacy C++, C and java are supported.
Bindings for more languages and/or virtual machines should be added to allow broader AI developing audience (for example: Ruby, Perl, JavaScript, Python, D, Go, Mono, LLVM, Parrot).
Required skills
- Understanding of the Spring AI interface
- knowledge of C
- Understanding of the target language/virtual machine
Difficulty
Estimated: medium
The current C AI interface has been structured so it acts as a bridge between the engine and the various AI language wrappers, since automatic wrapper generators have been tried in the past and found infeasible, manual creation is necessary.
