11–16 of 16 posts
hmm no disrespect intended but .. this line of the article jumps out .. "C++ is a good choice for a standard implementation of the protocol, it is a common denominator of most of the languages out there, it has a massive developer community and is widely adopted in the industry for performance middleware applications." AFAIK the linking characteristics of C++ are pretty bad, since the symbols are mangled in a compile…
hmm no disrespect intended but .. this line of the article jumps out .. "C++ is a good choice for a standard implementation of the protocol, it is a common denominator of most of the languages out there, it has a massive developer community and is widely adopted in the industry for performance middleware applications." AFAIK the linking characteristics of C++ are pretty bad, since the symbols are mangled in a compile…
Having said this, for C++ there is extern "language" {}, with extern "C" {} being the most common.
The title is wrong here. We don't claim that xeus-python will replace IPython. IPython/IPykernel has plenty of great features and xeus-python covers just a small portion of it.
The title is misleading and wrong. The article is about a new library that lets you write kernels in C++. There is however a kernel for C++ that you can try here: https://mybinder.org/v2/gh/QuantStack/xeus-cling/stable?file... if interpreted C++ is your thing :)
Read the whole article. It starts by introducing xeus and xeus-cling for those who don't already know about it, then gets to the subject of the title, xeus-python, which is based on xeus and, indeed, written in C++: https://github.com/QuantStack/xeus-python
The title is misleading and wrong. The article is about a new library that lets you write kernels in C++. There is however a kernel for C++ that you can try here: https://mybinder.org/v2/gh/QuantStack/xeus-cling/stable?file... if interpreted C++ is your thing :)
This bug is prohibitive enough I suspect it will be a deal breaker for the majority who want to use this kind of tech.