4 ms·
I've been using Cython since it was called Pyrex, and I'm perpetually annoyed with rewriting c/c++ headers in Cython. This seems neat. But the reason that I u
by klyrs 7y ago
I've been using Cython since it was called Pyrex, and I'm perpetually annoyed with rewriting c/c++ headers in Cython. This seems neat. But the reason that I use Cython is that I can wrap complex data structures (including templated c++ classes) and do processing in a fuzzy boundary between Python and c/c++.
The "code-free" approach here seems to forbid such a fuzzy boundary. Am I wrong?
- atilaneves 7y agoI can't really comment without an example. I don't think this approach stops you from doing anything. It can (and has) allowed Python to call into templated D code, as long as you give the particular instantiation you're interested in an alias.
- biotronic 7y agoSince Cython compiles to C++, it can use C++ templates directly, without the need for creating aliases to the specific instantiations you're gonna use. As far as I understand, you'll still have to write Cython bindings, though: https://cython.readthedocs.io/en/latest/src/userguide/wrapping_CPlusPlus.html#templates https://cython.readthedocs.io/en/latest/src/userguide/wrappi...