On Thu, 18 May 2017 06:10 pm, Christian Gollwitzer wrote: > Am 18.05.17 um 00:21 schrieb Chris Angelico: >> On Thu, May 18, 2017 at 8:06 AM, Christian Gollwitzer <aurio...@gmx.de> >> wrote: >>> tcc even has a "JIT-mode" of operation (libtcc). For Tcl, there exists >>> an extension which compiles C code to memory and executes directly from >>> there. The same thing could be done for Python, too. >> >> One of the complaints that bartc raised against clang was that it's >> not self-contained - that it depends on some other stdlib. Yet he >> espouses a tiny C compiler that obviously has the same limitation. On >> my Linux boxes, I can grab GNU libc; but on Windows, where are you >> going to get the header files and link-time libraries from? Oh right. >> MSVC. > > It was me who brought up tcc as a possible useful enhancement of Python. > I have been using it without external library files to compile > extensions for Tcl, and have proposed that it could be equally useful > for Python. > > The whole discussion reminds me of the "bumblebees can't fly" thing.
To quote the Commandant from "Private Schultz" (a wonderful, but now impossible to track down, BBC comedy series): "Consider the bumblebee. It flies, damn you, because it does not know that it cannot!" -- Steve Emoji: a small, fuzzy, indistinct picture used to replace a clear and perfectly comprehensible word. -- https://mail.python.org/mailman/listinfo/python-list
