Hacker News new | ask | show | jobs
by gpshead 3339 days ago
I wondered how long it would take before someone posted CLIF here since we haven't put up a blog post about it yet... :)

Interesting stat: Around 80% of our the Python C++ extension module wrappings being added to our code base are now being done using CLIF instead of SWIG. We are actively working on forbidding new Python SWIG wrappers from being added and migrating important legacy wrappings off of it onto CLIF.

Who am I? I am TL of the team that create CLIF (design and code reviewer, _not_ a primary author; they can identify themselves as they see fit). -gps@

2 comments

When are y'all doing Go and Java, though? The fact that this exists just compounds the pain of writing SWIG for the other two languages. The grass really is greener.
Go and Java claimed they can do without C++, so let them suffer :)

It takes time and because we love Python we did it first. Others will come.

SWIG is ... special.
So... someone with basically zero Python experience and a ton of C++ experience could basically "hand that experience down" to his newly minted Python-self?
Sounds like a worthy goal. There will always be infelicities (as with human language translation as well) but why not?