Can we invoke Ecere components from other languages?
-
- Posts: 29
- Joined: Tue Jul 06, 2010 4:11 am
Can we invoke Ecere components from other languages?
I introduced Ecere to my friends, and they have a question: Can we invoke Ecere components from other languages? For example, haskell/C/C++/Java?
Re: Can we invoke Ecere components from other languages?
Thanks nowind_lee for sharing Ecere =)
At the moment, it's only possible if you go through the trouble of interfacing with eC components at the C level. This means that in your eC code you write a 'C' function (if you have not defined a namespace, this is a simple as declaring a non-static function, outside of a class), which you can call from any other language which has support for calling C functions. If you have defined a namespace, you can put 'default' in front of your function definition to prevent the eC compiler from mangling the function with the namespace.
Similarly, it is possible for eC to invoke C style functions in any linked in libraries.
The Ecere IDE will handle projects containing C, eC and C++ files together, and can produce executables, static and shared libraries with them.
Automaticaly generating bindings for all those languages is part of our plan, however!
C++, Objective-C, Java and C# (CLI) are languages we're most interested in having bindings for.
Regards,
Jerome
At the moment, it's only possible if you go through the trouble of interfacing with eC components at the C level. This means that in your eC code you write a 'C' function (if you have not defined a namespace, this is a simple as declaring a non-static function, outside of a class), which you can call from any other language which has support for calling C functions. If you have defined a namespace, you can put 'default' in front of your function definition to prevent the eC compiler from mangling the function with the namespace.
Similarly, it is possible for eC to invoke C style functions in any linked in libraries.
The Ecere IDE will handle projects containing C, eC and C++ files together, and can produce executables, static and shared libraries with them.
Automaticaly generating bindings for all those languages is part of our plan, however!
C++, Objective-C, Java and C# (CLI) are languages we're most interested in having bindings for.
Regards,
Jerome