内容简介:Inmy last blog post I wrote about the power of D’s compile-time reflection and string mixins, showing how they could be used to call D from Python so easily it might as well be magic. As amazing as that may be for those of us who have D codebases we want t
Inmy last blog post I wrote about the power of D’s compile-time reflection and string mixins, showing how they could be used to call D from Python so easily it might as well be magic. As amazing as that may be for those of us who have D codebases we want to expose to Python users, this doesn’t help the vastly more numerous programmers who want to call pre-existing C code instead. If C had D’s metaprogramming abilities, imagine seamlessly calling into nanomsg with as much as ease as I showed in my previous blog post. Well… about that.
D can easily interoperate with C , with the only requirement being that the function and data structure declarations be translated into D syntax. But once the translation is done, those declarations are now D code that can be reflected on, fed to autowrap , and automagically wrapped for Python consumption. That would be a pretty powerful combo if not for the boring work of translating all needed declarations, macros included. It’s still a lot easier than talking to the Python C API itself of course, but maybe not quite killer feature material.
However, I wrote a little project called dpp because I’m lazy and don’t want to hand-translate C to D. Envious of C++’s and Objective C’s credible claim to be the only languages that can seamlessly interoperate with C (due to header inclusion and compatible syntax), I tried to replicate the experience in the D world. Using dpp, one can #include C headers in what would otherwise be D code and use it as one would in C++, even going to the point of supporting preprocessor macros. I wrote about the project in adifferent blog post.
Given this .dpp file:
// nanomsg.dpp #include "nanomsg/nn.h" #include "nanomsg/pipeline.h"
And this .d file:
import autowrap; mixin( wrapDlang!( LibraryName("nanomsg"), // name of the .so Modules(Yes.alwaysExport, "nanomsg") // name of the D module ) );
When we build both of those files above into nanomsg.so
, we get to write this Python code that actually sends packets:
from nanomsg import (nn_socket, nn_close, nn_bind, nn_connect, nn_send, nn_recv, AF_SP, NN_PUSH, NN_PULL) import time uri = "inproc://test" pull = nn_socket(AF_SP, NN_PULL) nn_bind(pull, uri) time.sleep(0.05) # give it time to set up (awful I know, but meh) push = nn_socket(AF_SP, NN_PUSH) nn_connect(push, uri) msg = b'abc' nn_send(push, msg, len(msg), 0)
Python, welcome to C, via D, and without even having to write any code to do it. Did I mention that AF_SP, NN_PUSH, and NN_PULL are all C macros? And yet, look at Python importing and using them like a boss.
Want to try it yourself? It’s on github .
If you want to call C from Python, use D.
以上所述就是小编给大家介绍的《Want to call C from Python? Use D》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
The Pragmatic Programmer
Andrew Hunt、David Thomas / Addison-Wesley Professional / 1999-10-30 / USD 49.99
本书直击编程陈地,穿过了软件开发中日益增长的规范和技术藩篱,对核心过程进行了审视――即根据需求,创建用户乐于接受的、可工作和易维护的代码。本书包含的内容从个人责任到职业发展,直至保持代码灵活和易于改编重用的架构技术。从本书中将学到防止软件变质、消除复制知识的陷阱、编写灵活、动态和易适应的代码、避免出现相同的设计、用契约、断言和异常对代码进行防护等内容。一起来看看 《The Pragmatic Programmer》 这本书的介绍吧!