Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #58959 > unrolled thread
| Started by | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| First post | 2013-11-09 10:35 -0800 |
| Last post | 2013-11-11 13:37 +1300 |
| Articles | 3 — 3 participants |
Back to article view | Back to comp.lang.python
python operational semantics paper Paul Rubin <no.email@nospam.invalid> - 2013-11-09 10:35 -0800
Re: python operational semantics paper Terry Reedy <tjreedy@udel.edu> - 2013-11-10 05:42 -0500
Re: python operational semantics paper Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2013-11-11 13:37 +1300
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2013-11-09 10:35 -0800 |
| Subject | python operational semantics paper |
| Message-ID | <7x61s1o22j.fsf@ruckus.brouhaha.com> |
This looks kind of interesting. http://cs.brown.edu/~sk/Publications/Papers/Published/pmmwplck-python-full-monty/ Abstract We present a small-step operational semantics for the Python programming language. We present both a core language for Python, suitable for tools and proofs, and a translation process for converting Python source to this core. We have tested the composition of translation and evaluation of the core for conformance with the primary Python implementa- tion, thereby giving confidence in the fidelity of the seman- tics. We briefly report on the engineering of these compo- nents. Finally, we examine subtle aspects of the language, identifying scope as a pervasive concern that even impacts features that might be considered orthogonal.
[toc] | [next] | [standalone]
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2013-11-10 05:42 -0500 |
| Message-ID | <mailman.2329.1384080179.18130.python-list@python.org> |
| In reply to | #58959 |
On 11/9/2013 1:35 PM, Paul Rubin wrote: > This looks kind of interesting. > > http://cs.brown.edu/~sk/Publications/Papers/Published/pmmwplck-python-full-monty/ > > Abstract > > We present a small-step operational semantics for the Python programming > language. We present both a core language for Python, suitable for tools > and proofs, and a translation process for converting Python source to > this core. We have tested the composition of translation and evaluation > of the core for conformance with the primary Python implementa- tion, > thereby giving confidence in the fidelity of the seman- tics. We briefly > report on the engineering of these compo- nents. Finally, we examine > subtle aspects of the language, identifying scope as a pervasive concern > that even impacts features that might be considered orthogonal. Thanks for posting this. I found it very interesting but will need more time to digest it. I plan to open a separate thread based on one item in the paper. -- Terry Jan Reedy
[toc] | [prev] | [next] | [standalone]
| From | Gregory Ewing <greg.ewing@canterbury.ac.nz> |
|---|---|
| Date | 2013-11-11 13:37 +1300 |
| Message-ID | <bean60Fpi8mU1@mid.individual.net> |
| In reply to | #58959 |
Paul Rubin wrote:
>
> http://cs.brown.edu/~sk/Publications/Papers/Published/pmmwplck-python-full-monty/
>
> Abstract
>
> We present a small-step operational semantics for the Python programming
> language.
I noticed one thing they seem to have missed. They
assume that
a + b
is equivalent to
a.__add__(b)
when, as many of us know, it's considerably more
complicated than that.
--
Greg
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.python
csiph-web