|
|||
|
I created py2c ( http://code.google.com/p/py2c )- an open source Python to C/C++ translator!
py2c is looking for developers! To join create a posting in the py2c-discuss Google Group or email me! Thanks PS:I hope this is the appropiate group for this message. |
|
|
||||
|
||||
|
|
|
|||
|
2012/7/30 <maniandram01@gmail.com>:
> I created py2c ( http://code.google.com/p/py2c )- an open source Python to C/C++ translator! > py2c is looking for developers! > To join create a posting in the py2c-discuss Google Group or email me! > Thanks > PS:I hope this is the appropiate group for this message. > -- > http://mail.python.org/mailman/listinfo/python-list It looks like a very very hard task, and really useful or for exercise? The first few lines I've seen there are the dangerous * imports and LazyStrin looks like a typo.. from ast import * import functools from c_types import * from lazystring import * #constant data empty = LazyStrin ordertuple = ((Or,),(And |
|
|||
|
On Jul 30, 7:27*am, maniandra...@gmail.com wrote:
> I created py2c (http://code.google.com/p/py2c)- an open source Python to C/C++ translator! > py2c is looking for developers! > To join create a posting in the py2c-discuss Google Group or email me! > Thanks > PS:I hope this is the appropiate group for this message. Out of curiosity. What is the difference between this and Shedskin? Shedskin being a (restricted) python-to-C++ compiler. (http://code.google.com/p/ shedskin/) Is the goal to be able to handle any python code or a subset? Cheers, Adam |
|
|||
|
On Jul 31, 2:42*am, MaxTheMouse <maxthemo...@googlemail.com> wrote:
> What is the difference between this and Shedskin? Shedskin being a > (restricted) python-to-C++ compiler. (http://code.google.com/p/ > shedskin/) Is the goal to be able to handle any python code or a > subset? There's also Nuitka, which is an unrestricted compiler, I believe: http://nuitka.net/pages/overview.html Is this a completely independent project, or are there plans to leverage off of PyPy's toolchain, for example? |
|
|||
|
alex23, 31.07.2012 02:16:
> On Jul 31, 2:42 am, MaxTheMouse wrote: >> What is the difference between this and Shedskin? Shedskin being a >> (restricted) python-to-C++ compiler. (http://code.google.com/p/ >> shedskin/) Is the goal to be able to handle any python code or a >> subset? > > There's also Nuitka, which is an unrestricted compiler, I believe: > http://nuitka.net/pages/overview.html Not to forget Cython, which is the only Python-to-C compiler that is in widespread use. > Is this a completely independent project, or are there plans to > leverage off of PyPy's toolchain, for example? >From a look at the source code, it seems hard to bring it together with anything. It looks very monolithic. Stefan |
|
|||
|
Stefan Behnel, 31.07.2012 07:23:
> From a look at the source code, it seems hard to bring it together with > anything. It looks very monolithic. Hmm, sorry, I mixed it up with "2c.py", which is yet another of those Python-to-C compilers with an all too similar name. https://code.google.com/p/2c-python/ There are a couple of others here: http://wiki.python.org/moin/PythonImplementations Seeing the number of those compilers, almost none of which is commonly used and/or still alive as a project, the question really is: why another one? I mean, it's totally fine as a hobby educational project, sure, and I really don't want to discourage anyone from going through this to have fun. But apart from "just for fun", what is the goal that would make this particular compiler different from the others? And also different enough to merit its own source base, instead of basing it on one of the existing projects? I don't consider "source is harder to read than to write" a good answer to this in general. Stefan |
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|