Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #57152 > unrolled thread
| Started by | Philip Herron <herron.philip@googlemail.com> |
|---|---|
| First post | 2013-10-20 10:56 -0700 |
| Last post | 2013-11-15 07:59 -0800 |
| Articles | 9 on this page of 129 — 29 participants |
Back to article view | Back to comp.lang.python
Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-20 10:56 -0700
Re: Python Front-end to GCC victorgarcianet@gmail.com - 2013-10-20 15:10 -0700
Re: Python Front-end to GCC John Nagle <nagle@animats.com> - 2013-10-22 23:48 -0700
Re: Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-23 00:25 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-23 09:42 +0100
Re: Python Front-end to GCC John Nagle <nagle@animats.com> - 2013-10-23 13:51 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-20 20:35 -0700
Re: Python Front-end to GCC Steven D'Aprano <steve@pearwood.info> - 2013-10-21 07:46 +0000
Re: Python Front-end to GCC Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-10-21 10:55 +0100
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-21 23:41 +0000
Re: Python Front-end to GCC Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-10-22 10:14 +0100
Re: Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-22 02:32 -0700
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 12:00 +0000
Re: Python Front-end to GCC Chris Angelico <rosuav@gmail.com> - 2013-10-22 23:20 +1100
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 17:27 +0000
Re: Python Front-end to GCC Chris Angelico <rosuav@gmail.com> - 2013-10-23 08:43 +1100
Re: Python Front-end to GCC Dave Angel <davea@davea.name> - 2013-10-22 14:04 +0000
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 15:22 +0000
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 15:39 +0000
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 16:40 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-22 17:50 +0100
Re: Python Front-end to GCC Chris Kaynor <ckaynor@zindagigames.com> - 2013-10-22 09:52 -0700
Re: Python Front-end to GCC albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-11-01 22:48 +0000
Re: Python Front-end to GCC Frank Miles <fpm@u.washington.edu> - 2013-10-22 16:53 +0000
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 17:23 +0000
Re: Python Front-end to GCC Chris Kaynor <ckaynor@zindagigames.com> - 2013-10-22 10:35 -0700
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-22 17:37 +0000
Re: Python Front-end to GCC Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-10-22 18:37 +0100
Re: Python Front-end to GCC MRAB <python@mrabarnett.plus.com> - 2013-10-22 18:42 +0100
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 18:49 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 04:40 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 04:55 -0700
Re: Python Front-end to GCC Dan Sommers <dan@tombstonezero.net> - 2013-10-25 12:55 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 15:18 +0100
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-25 10:35 -0400
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 11:26 -0700
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-25 19:06 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 19:40 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 11:45 -0700
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-25 11:59 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 12:09 -0700
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-25 12:15 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 20:02 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 12:18 -0700
Re: Python Front-end to GCC John Nagle <nagle@animats.com> - 2013-10-26 14:31 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-26 15:10 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-27 15:14 -0700
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-27 19:15 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-28 08:44 +0000
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-28 02:31 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 20:36 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 12:49 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 21:14 +0100
Re: Python Front-end to GCC Tim Delaney <timothy.c.delaney@gmail.com> - 2013-10-26 07:11 +1100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 13:29 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 21:36 +0100
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-26 02:42 +0000
[OT] Re: Python Front-end to GCC Antoine Pitrou <solipsis@pitrou.net> - 2013-10-29 11:04 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 21:44 +0100
Re: Python Front-end to GCC Tim Delaney <timothy.c.delaney@gmail.com> - 2013-10-26 07:48 +1100
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 21:56 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 14:02 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 22:11 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-25 14:37 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-25 22:56 +0100
Re: Python Front-end to GCC Chris Angelico <rosuav@gmail.com> - 2013-10-26 13:36 +1100
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-22 17:15 +0000
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 18:58 +0000
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 20:26 +0000
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 15:36 +0000
Re: Python Front-end to GCC Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-10-22 15:15 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-21 13:14 -0700
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-21 16:29 -0400
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-21 20:40 -0700
Re: Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-21 04:08 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-21 13:26 -0700
Re: Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-21 14:03 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-21 16:04 -0700
Re: Python Front-end to GCC Piet van Oostrum <piet@vanoostrum.org> - 2013-10-21 23:45 -0400
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-21 21:24 -0700
Re: Python Front-end to GCC Steven D'Aprano <steve@pearwood.info> - 2013-10-22 05:25 +0000
Re: Python Front-end to GCC Dave Angel <davea@davea.name> - 2013-10-22 04:39 +0000
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-22 08:04 -0700
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 17:09 +0000
Re: Python Front-end to GCC Piet van Oostrum <piet@vanoostrum.org> - 2013-10-22 13:20 -0400
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-22 11:46 -0400
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-22 16:52 +0100
Re: Python Front-end to GCC Benjamin Kaplan <benjamin.kaplan@case.edu> - 2013-10-22 09:03 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-22 10:50 -0700
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-22 11:11 -0700
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-22 18:18 +0000
Re: Python Front-end to GCC Piet van Oostrum <piet@vanoostrum.org> - 2013-10-22 15:20 -0400
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-22 19:27 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-22 20:38 +0100
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-22 20:00 +0000
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-22 20:32 +0100
Re: Python Front-end to GCC Skip Montanaro <skip@pobox.com> - 2013-10-22 13:08 -0500
Re: Python Front-end to GCC MRAB <python@mrabarnett.plus.com> - 2013-10-22 19:16 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-22 11:16 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-22 11:22 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-22 11:28 -0700
Re: Python Front-end to GCC Piet van Oostrum <piet@vanoostrum.org> - 2013-10-22 18:11 -0400
Re: Python Front-end to GCC Chris Angelico <rosuav@gmail.com> - 2013-10-23 17:28 +1100
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-22 22:47 +0000
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-22 14:23 -0400
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-22 11:40 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-22 19:58 +0100
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-22 14:40 -0400
Re: Python Front-end to GCC alex23 <wuwei23@gmail.com> - 2013-10-23 11:36 +1000
Re: Python Front-end to GCC rusi <rustompmody@gmail.com> - 2013-10-22 21:04 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-23 07:06 +0100
Re: Python Front-end to GCC MRAB <python@mrabarnett.plus.com> - 2013-10-22 19:47 +0100
Re: Python Front-end to GCC Ned Batchelder <ned@nedbatchelder.com> - 2013-10-22 13:56 -0400
Re: Python Front-end to GCC Michael Torrie <torriem@gmail.com> - 2013-10-22 22:05 -0600
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-23 07:13 +0100
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-26 14:25 -0700
Re: Python Front-end to GCC Mark Janssen <dreamingforward@gmail.com> - 2013-10-26 14:33 -0700
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-26 22:38 +0100
Re: Python Front-end to GCC Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-10-26 22:35 +0100
Re: Python Front-end to GCC Grant Edwards <invalid@invalid.invalid> - 2013-10-28 14:21 +0000
Re: Python Front-end to GCC Chris Angelico <rosuav@gmail.com> - 2013-10-29 01:26 +1100
Re: Python Front-end to GCC Neil Cerutti <neilc@norwich.edu> - 2013-10-28 15:01 +0000
Re: Python Front-end to GCC Antoine Pitrou <solipsis@pitrou.net> - 2013-10-22 08:55 +0000
Re: Python Front-end to GCC Philip Herron <herron.philip@googlemail.com> - 2013-10-22 02:08 -0700
Re: Python Front-end to GCC Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-10-22 10:10 +0000
Re: Python Front-end to GCC Antoine Pitrou <solipsis@pitrou.net> - 2013-10-22 15:51 +0000
Re: Python Front-end to GCC Stefan Behnel <stefan_ml@behnel.de> - 2013-10-24 08:47 +0200
Re: Python Front-end to GCC xDog Walker <thudfoo@gmail.com> - 2013-10-25 14:49 -0700
Re: Python Front-end to GCC sharath.cs.smp@gmail.com - 2013-11-15 07:59 -0800
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2013-10-29 01:26 +1100 |
| Message-ID | <mailman.1703.1382970405.18130.python-list@python.org> |
| In reply to | #57825 |
On Tue, Oct 29, 2013 at 1:21 AM, Grant Edwards <invalid@invalid.invalid> wrote: > On 2013-10-26, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote: >> On 26/10/2013 22:25, Mark Janssen wrote: >> >> Please give it a rest Mark, nobody is falling for your pseudo babel. > > I think you do him a disservice. I'm pretty sure it's genuine, > bona-fide, 24K, dyed-in-the-wool, 99 and 44/100 pure babble. I think it's even better than that... maybe even 28.8K! ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Neil Cerutti <neilc@norwich.edu> |
|---|---|
| Date | 2013-10-28 15:01 +0000 |
| Message-ID | <bd7cj1Fq8kkU2@mid.individual.net> |
| In reply to | #57828 |
On 2013-10-28, Chris Angelico <rosuav@gmail.com> wrote: > On Tue, Oct 29, 2013 at 1:21 AM, Grant Edwards <invalid@invalid.invalid> wrote: >> On 2013-10-26, Mark Lawrence <breamoreboy@yahoo.co.uk> wrote: >>> On 26/10/2013 22:25, Mark Janssen wrote: >>> >>> Please give it a rest Mark, nobody is falling for your pseudo >>> babel. >> >> I think you do him a disservice. I'm pretty sure it's genuine, >> bona-fide, 24K, dyed-in-the-wool, 99 and 44/100 pure babble. > > I think it's even better than that... maybe even 28.8K! From my own bailiwick I'd say it's Grade A Medium Amber. -- Neil Cerutti
[toc] | [prev] | [next] | [standalone]
| From | Antoine Pitrou <solipsis@pitrou.net> |
|---|---|
| Date | 2013-10-22 08:55 +0000 |
| Message-ID | <mailman.1344.1382432137.18130.python-list@python.org> |
| In reply to | #57191 |
Philip Herron <herron.philip <at> googlemail.com> writes: > > Its interesting a few things come up what about: > > exec and eval. I didn't really have a good answer for this at my talk at PYCon IE 2013 but i am going to say no. I am > not going to implement these. Partly because eval and exec at least to me are mostly from developing > interpreters as a debugging exercise so the test doesn't have to invoke the program properly and feed in > strings to interpret at least thats what i have done in the past with an virtual machine i wrote before gccpy. If you don't implement exec() and eval() then people won't be able to use namedtuples, which are a common datatype factory. As for the rest: well, good luck writing an AOT compiler producing interesting results on average *pure* Python code. It's already been tried a number of times, and has generally failed. Cython mitigates the issue by exposing a superset of Python (including type hints, etc.). Regards Antoine.
[toc] | [prev] | [next] | [standalone]
| From | Philip Herron <herron.philip@googlemail.com> |
|---|---|
| Date | 2013-10-22 02:08 -0700 |
| Message-ID | <f6e63d25-4fe1-45f9-a6e8-03278bb323d9@googlegroups.com> |
| In reply to | #57246 |
On Tuesday, 22 October 2013 09:55:15 UTC+1, Antoine Pitrou wrote: > Philip Herron <herron.philip <at> googlemail.com> writes: > > > > > > Its interesting a few things come up what about: > > > > > > exec and eval. I didn't really have a good answer for this at my talk at > > PYCon IE 2013 but i am going to say no. I am > > > not going to implement these. Partly because eval and exec at least to me > > are mostly from developing > > > interpreters as a debugging exercise so the test doesn't have to invoke > > the program properly and feed in > > > strings to interpret at least thats what i have done in the past with an > > virtual machine i wrote before gccpy. > > > > If you don't implement exec() and eval() then people won't be able to use > > namedtuples, which are a common datatype factory. > > > > As for the rest: well, good luck writing an AOT compiler producing > > interesting results on average *pure* Python code. It's already been tried > > a number of times, and has generally failed. Cython mitigates the issue by > > exposing a superset of Python (including type hints, etc.). > > > > Regards > > > > Antoine. Thanks for that interesting example, i haven't looked into how its implemented but on initially looking at this is am nearly sure i can implement this without using exec or eval. I've found this a lot in implementing my run time. Exec and eval at least to me in the past I've used them as debug hooks into a toy virtual machine i wrote i don't particularly think they are part of a language nor should people really use them. Thanks
[toc] | [prev] | [next] | [standalone]
| From | Steven D'Aprano <steve+comp.lang.python@pearwood.info> |
|---|---|
| Date | 2013-10-22 10:10 +0000 |
| Message-ID | <52664f2a$0$29981$c3e8da3$5496439d@news.astraweb.com> |
| In reply to | #57246 |
On Tue, 22 Oct 2013 08:55:15 +0000, Antoine Pitrou wrote: > If you don't implement exec() and eval() then people won't be able to > use namedtuples, which are a common datatype factory. Philip could always supply his own implementation of namedtuple that doesn't use exec. But either way, if he doesn't implement eval and exec, what he has is not Python, but a subset of Python. Perhaps an interesting and useful subset. -- Steven
[toc] | [prev] | [next] | [standalone]
| From | Antoine Pitrou <solipsis@pitrou.net> |
|---|---|
| Date | 2013-10-22 15:51 +0000 |
| Message-ID | <mailman.1358.1382457135.18130.python-list@python.org> |
| In reply to | #57250 |
Steven D'Aprano <steve+comp.lang.python <at> pearwood.info> writes: > > On Tue, 22 Oct 2013 08:55:15 +0000, Antoine Pitrou wrote: > > > If you don't implement exec() and eval() then people won't be able to > > use namedtuples, which are a common datatype factory. > > Philip could always supply his own implementation of namedtuple that > doesn't use exec. > > But either way, if he doesn't implement eval and exec, what he has is not > Python, but a subset of Python. Perhaps an interesting and useful subset. If you go that way, we already have Cython (which is both a subset and superset of Python, although I don't know if it's still a strict subset these days). Regards Antoine.
[toc] | [prev] | [next] | [standalone]
| From | Stefan Behnel <stefan_ml@behnel.de> |
|---|---|
| Date | 2013-10-24 08:47 +0200 |
| Message-ID | <mailman.1443.1382597292.18130.python-list@python.org> |
| In reply to | #57191 |
Antoine Pitrou, 22.10.2013 10:55: > Philip Herron writes: >> Its interesting a few things come up what about: >> exec and eval. I didn't really have a good answer for this at my talk at >> PYCon IE 2013 but i am going to say no. I am >> not going to implement these. Partly because eval and exec at least to me >> are mostly from developing >> interpreters as a debugging exercise so the test doesn't have to invoke >> the program properly and feed in >> strings to interpret at least thats what i have done in the past with an >> virtual machine i wrote before gccpy. > > If you don't implement exec() and eval() then people won't be able to use > namedtuples, which are a common datatype factory. FWIW, for Cython, I personally consider eval() and exec() more of a handy way to insert plain Python code (potentially even generated at runtime) into compiled code, so they are not currently compiled. You can see that from the low Mako benchmark results, for example. We may eventually add an option to compile that code at runtime (assuming you have Cython and a C compiler installed), but I doubt that people would want that as the default. Obviously, Cython has the advantage of being backed by a CPython runtime, so it's easy for us to choose one or the other. An independent Python implementation doesn't easily have that choice. > As for the rest: well, good luck writing an AOT compiler producing > interesting results on average *pure* Python code. It's already been tried > a number of times, and has generally failed. Cython mitigates the issue by > exposing a superset of Python (including type hints, etc.). Agreed, although the word "mitigate" makes it sound more like a work-around than the actual feature it represents. I've written down my thoughts on this topic a while ago. http://blog.behnel.de/index.php?p=241 Stefan
[toc] | [prev] | [next] | [standalone]
| From | xDog Walker <thudfoo@gmail.com> |
|---|---|
| Date | 2013-10-25 14:49 -0700 |
| Message-ID | <mailman.1557.1382738550.18130.python-list@python.org> |
| In reply to | #57152 |
On Friday 2013 October 25 14:11, Mark Lawrence wrote: > Will you please do yourself a favour and get a new dealer before you do > some real damage, the batch you're currently on is definitely contaminated. Meet Mark Janssen: http://sourceforge.net/apps/mediawiki/pangaia/index.php?title=User:Average -- Yonder nor sorghum stenches shut ladle gulls stopper torque wet strainers.
[toc] | [prev] | [next] | [standalone]
| From | sharath.cs.smp@gmail.com |
|---|---|
| Date | 2013-11-15 07:59 -0800 |
| Message-ID | <776e8433-e716-4edd-8615-1765fba16087@googlegroups.com> |
| In reply to | #57152 |
On Sunday, 20 October 2013 10:56:46 UTC-7, Philip Herron wrote: > Hey, > > > > I've been working on GCCPY since roughly november 2009 at least in its > > concept. It was announced as a Gsoc 2010 project and also a Gsoc 2011 > > project. I was mentored by Ian Taylor who has been an extremely big > > influence on my software development carrer. > > > > Gccpy is an Ahead of time implementation of Python ontop of GCC. So it > > works as you would expect with a traditional compiler such as GCC to > > compile C code. Or G++ to compile C++ etc. > > > > Whats interesting and deserves a significant mention is my work is > > heavily inspired by Paul Biggar's phd thesis on optimizing dynamic > > languages and his work on PHC a ahead of time php compiler. I've had > > so many ups and down in this project and i need to thank Andi Hellmund > > for his contributions to the project. > > http://paulbiggar.com/research/#phd-dissertation > > > > The project has taken so many years as an in my spare time project to > > get to this point. I for example its taken me so long simply to > > understand a stabilise the core fundamentals for the compiler and how > > it could all work. > > > > The release can be found here. I will probably rename the tag to the > > milestone (lucy) later on. > > https://github.com/redbrain/gccpy/releases/tag/v0.1-24 > > (Lucy is our dog btw, German Shepard (6 years young) loves to lick > > your face off :) ) > > > > Documentation can be found http://gcc.gnu.org/wiki/PythonFrontEnd. > > (Although this is sparse partialy on purpose since i do not wan't > > people thinking this is by any means ready to compile real python > > applications) > > > > I've found some good success with this project in compiling python > > though its largely unknown to the world simply because i am nervous of > > the compiler and more specifically the python compiler world. > > > > But at least to me there is at least to me an un-answered question in > > current compiler implementations. AOT vs Jit. > > > > Is a jit implementation of a language (not just python) better than > > traditional ahead of time compilation. > > > > What i can say is ahead of time at least strips out the crap needed > > for the users code to be run. As in people are forgetting the basics > > of how a computer works in my opinion when it comes to making code run > > faster. Simply need to reduce the number of instructions that need to > > be executed in order to preform what needs to be done. Its not about > > Jit and bla bla keyword llvm keyword instruction scheduling keyword > > bla. > > > > I could go into the arguments but i feel i should let the project > > speak for itself its very immature so you really cant compare it to > > anything like it but it does compile little bits and bobs fairly well > > but there is much more work needed. > > > > There is nothing at steak, its simply an idea provoked from a great > > phd thesis and i want to see how it would work out. I don't get funded > > of paid. I love working on compilers and languages but i don't have a > > day job doing it so its my little pet to open source i believe its at > > least worth some research. > > > > I would really like to hear the feedback good and bad. I can't > > describe how much work i've put into this and how much persistence > > I've had to have in light of recent reddit threads talking about my > > project. > > > > I have so many people to thank to get to this point! Namely Ian > > Taylor, Paul Biggar, Andi Hellmund, Cyril Roelandt Robert Bradshaw, > > PyBelfast, and the Linux Outlaws community. I really couldn't have got > > to this point in my life without the help of these people! > > > > Thanks! > > > > --Phil
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | comp.lang.python
csiph-web