somehow bookaa was removed from the recipient list, so a quick rehearsal
with him added again
Armin wrote:
Hi,
On Mon, Apr 23, 2012 at 01:35, s...@pobox.com wrote:
Maciej I would really like this sort of changes to come with it's own
Maciej tests (ones that check what was compiled
Hi,
On Mon, Apr 23, 2012 at 01:35, s...@pobox.com wrote:
Maciej I would really like this sort of changes to come with it's own
Maciej tests (ones that check what was compiled preferably).
What might such tests look like?
It is an issue: unit-testing this kind of detail is a bit hard,
Hi Bookaa,
On 04/23/2012 08:19 AM, Armin Rigo wrote:
Bookaa, the person to do that can be you. In that case you need to
learn about Mercurial version control and the http://bitbucket.org
repository. I would recommend that you register on bitbucket, and
create your own fork of pypy/pypy to
Maciej I would really like this sort of changes to come with it's own
Maciej tests (ones that check what was compiled preferably).
What might such tests look like? That is, how would they be different than
tests which demonstrate that the current translation code is correct? (Are
there
2012/4/21 bookaa rors...@gmail.com
**
thank you for encourage!
as for the bugs, please tell me exacty how to run, which test.
My system is Win7, pypy tests get many error even without any change.
Tests in the translator/c directory should pass. For example:
c:\python27\python
On Fri, Apr 20, 2012 at 6:13 AM, gmail rors...@gmail.com wrote:
**
I find pypy translator output c files consist too many 'goto' statement.
Its hard to read and understand these c files.
I try to make it output with c keywords:
if..else..
while...break...continue
and now the
What is the purpose? For the target c/c++ compiler it is all the same, is not
it? Or is the purpose to make a python-c++ converter?
Cheers,
Alex
perjantai 20 huhtikuu 2012 09:09:12 Maciej Fijalkowski kirjoitti:
On Fri, Apr 20, 2012 at 6:13 AM, gmail rors...@gmail.com wrote:
I find pypy
2012/4/20 gmail rors...@gmail.com
I am still work hard try to improve pypy to get readable c++ output.
Anyone interest in this ?
The result is much better, especially with long functions.
Yes, this is interesting! Continue!
Your code needs to be polished though: comments, better names, pep8
@python.org
Subject: Re: [pypy-dev] output readable c
What is the purpose? For the target c/c++ compiler it is all the same, is not
it? Or is the purpose to make a python-c++ converter?
Cheers,
Alex
perjantai 20 huhtikuu 2012 09:09:12 Maciej Fijalkowski kirjoitti:
On Fri, Apr 20, 2012 at 6:13 AM
