On 17/10/22 10:13 pm, Denis Kotov wrote:
For example, PyObject is much better to implement using C++ class,
I used to think this. Python has OO features, C++ has OO features,
should be a good match, right?
Well, no. Python's OO is very flexible and dynamic, C++'s is very
rigid and static.
CPython is written (mostly) in C.
There's Jython written in Java. There also IronPython written on C#.
Feel free to write your own Python implementation in C++. Could be fun!
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an
On Mon, 17 Oct 2022 at 11:20, Denis Kotov wrote:
> Stephen J. Turnbull wrote:
> > Denis Kotov writes:
> > > See:
> > > https://youtube.com/clip/UgkxyNe_dsZKinT_RT3UGb-BaP0SnvKteo2o
> > > No thanks, if it's not text I'm not going to look at it. I don't have
> > time to watch videos with no
Stephen J. Turnbull wrote:
> Denis Kotov writes:
> > See:
> > https://youtube.com/clip/UgkxyNe_dsZKinT_RT3UGb-BaP0SnvKteo2o
> > No thanks, if it's not text I'm not going to look at it. I don't have
> time to watch videos with no explanation, and best guess is 90% of it
> I already know, just as I
Denis Kotov writes:
> For example, PyObject is much better to implement using C++ class,
> it will bring RAII that will reduce number of issues not free
> memory in CPython
Well, yes, that's the C++ Kool-Aid we're all supposed to drink. But
it has its costs, too. How does it affect
Stephen J. Turnbull wrote:
> Denis Kotov writes:
> > Usually people say that C++ not fit in CPython not knowing C++,
> > That's not the issue. There are plenty of people who know C++ who say
> the benefits of C++ are not worth the bugs, the effort, and the plain
> old churn that a rewrite in C++
