interpreters for
two different CPython versions - how would you name this?
Maybe keep the numbering, but give releases some fancy names, like
ubuntu, but regarding on what features are central within this
release.
Let's say:
pypy-1.1-two-point-fiver
pypy-2.0-jitted
Até já!
Jakub Gustak
i just created a blog where i intend to write about news
regarding testing and python and metaprogramming.
http://tetamap.blogspot.com/
Next blog to subscribe. Good.
and did a first posting about a new way of doing test state
setup with py.test. Um, does anybody know how to do code
I'm not sure about the technical details, but it sounds like a grea
idea. I think PyPy could benefit from more projects that explore
parallelism.
Still. No sign of PyPy at the PSF ideas page.
Is there any chance, PyPy will participate?
__
Jakub Gustak
,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
-parallel.html
http://www.haskell.org/ghc/docs/latest/html/libraries/parallel/Control-Parallel.html
EOM
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
like to get nested ellipses working and then start playing
with continuations. Wish me luck.
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
Some more info.
We have working simple macros. They are hygienic and referentially
transparent.
r5rs states that if macro introduces new binding, it should be renamed
to avoid conflicts with other identifiers. In our case we create
syntactic closure like described in:
. Still only (let
...) and (let* ...) are fully compatible with macro expanding. (letrec
...) is not.
In the future: more macros! (ellipsis, recursive expanding and CPS style macros)
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman
What's on with scheme interpreter:
Nice progress during post EuroPython sprint, see:
http://codespeak.net/pipermail/pypy-dev/2007q3/003919.html
And after the sprint:
(define (fun args) body) syntactic sugar added to lambda definitions.
(begin ...), (letrec ...) added. This leads to small
Here is what happened with scheme interpreter:
Antonio and I were working on scheme interpreter to translate. - (antocuni, jlg)
The biggest issue was with number handling, it resulted with numbers
hierarchy rethinking and arithmetical operations refactoring most of
them are dynamically
said, don't worry about making your code RPython too much yet.
I will try to refrain.
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
interesting stuff instead of refactoring and bug fixes.
I would like to refine what I would like to do during the sprint, but
not sure right now. Any ideas, what would be worth trying then?
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http
, there is
no distinction between variable or function when naming them),
dictionary would be the most straight forward. There is no need for a
special way to resolve naming conflicts and so on.
Or am I missing something?
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http
I would like to organize mini sprint (2-3 days) in Wroclaw.
It would be hold on Wroclaw University of Technology.
There are possible two alternative dates:
2-3th June
16(15)-17th June
It depends how fast we can organize ourselves.
Is there anybody, who would like to participate?
Cheers,
Jakub
on?
ebnfparse seems to work just fine, so I will stick with it, unless
there is any contraindication.
Now I am considering if the parser should generate some bytecode?
Maybe pickling (not rpythonic) AST tree will be just fine (like in js
interpreter)?
Sincerely,
Jakub Gustak
by the pypy.rlib.parsing.ebnfparse.
I will focus on that right now. Any links, documentation or literature
to help me understand this part?
Best regards,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
an introduction talk about
PyPy. But maybe one of you would like to take over the talk, as long
as I am a newbie.
Cheers,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
,
Jakub Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
I would like to collect some more feedback, then think about it during
the weekend, and then submit final application.
Submited.
_
Jakub Łukasz Gustak
___
pypy-dev@codespeak.net
http://codespeak.net/mailman/listinfo/pypy-dev
Just curious, but isn't proper tail recursion a consideration when
writing a Scheme interpreter? It's not a Python feature. But I can see,
though, that proper tail recursion is not needed to implement the
proposed features of the Project Details.
Indeed, good point. Scheme does not make much
20 matches
Mail list logo
