dtcaciuc at gmail.com
Mon Apr 23 19:12:10 CEST 2012
On Mon, Apr 23, 2012 at 10:09 AM, Dimitri Tcaciuc <dtcaciuc at gmail.com> wrote:
> I may be misuderstanding the intent here, but here it goes.
> If the main idea is to be able to call functions that are written in
> Julia or other languages, I think an effort to create an LLVM backend
> for Cython would go a long way towards inter-language connections as
> the one discussed here. It should be possible to take Cython- and
> Julia- produced LLVM bytecode and assemble it all together, applying
> whatever bytecode optimizers that are available (eg. SSE
> vectorization). A big advantage of that approach is that there's no
> need for one language to know syntax conventions of the other one (or
> at least not to full extent). Continuing the effort, it should be
> possible to eliminate the need for writing an intermediate .c/.cpp
> file if Clang compiler is used, which is also LLVM based.
I should clarify myself to avoid a gross mistake; a .c module would
still be necessary for CPython integration.
> On Mon, Apr 23, 2012 at 9:30 AM, Robert Bradshaw <robertwb at gmail.com> wrote:
>> On Sun, Apr 22, 2012 at 1:59 AM, Lisandro Dalcin <dalcinl at gmail.com> wrote:
>>> On 22 April 2012 08:10, Robert Bradshaw <robertwb at gmail.com> wrote:
>>>> Yes, Julia looks really cool. It's been on my radar for a while, but I
>>>> haven't had a chance to really try it out for anything yet. But I
>>>> hadn't thought about low-level Python/Cython <-> Julia integration.
>>>> That sounds very interesting. I wonder if Jython could give any
>>>> insight into to the tight interaction between two languages that are
>>>> usually used in isolation but have been made to call each other
>>>> (though there are a lot of differences too, e.g. we're not targeting
>>>> replacing the CPython interpreter (on first pass at least...)).
>>> Are you all aware that "calling C" actually means a ctypes-like
>>> functionality based in dlopen()/dlsym() ?
>> Yes, with all its drawbacks, but the fact that it's JIT'ed at least
>> cuts into the overhead issues.
>> - Robert
>> cython-devel mailing list
>> cython-devel at python.org
More information about the cython-devel