Kay Hayen, 22.07.2010 11:21:
>> This may indicate that the generated C++ code actually interfaces with
>> CPython. Maybe Kay can clear this up.

I take it from your response that your implementation is actually closer to 
Cython than I thought, except that it is currently focused purely on being 
a Python compiler.


> Well, the core of building a class, is e.g. this code:
>
>      PyObject *result = PyObject_CallFunctionObjArgs( metaclass,
> class_name, bases, dict, NULL );
>
> So, I let CPython call the metaclass, and do not yet even attempt to get
> in its way with it.

Ah, ok, so this is only meant for Python classes, right? That's simple 
enough, sure. The tricky thing in Cython is the 'expected' interaction with 
extension types, i.e. a language design question. That's currently not 
clear at all.

Stefan
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to