On 06/02/2011 06:47 AM, holger krekel wrote:
Is your implementation actually open source? Is it online somewhere?
it's at https://bitbucket.org/asuhan/happy
Great, thank you very much.
Carl Friedrich
___
pypy-dev mailing list
[email protected]
ht
On Thu, Jun 02, 2011 at 00:29 +0200, Carl Friedrich Bolz wrote:
> On 06/01/2011 06:20 PM, Alex Şuhan wrote:
> >On 06/01/2011 06:51 PM, Laura Creighton wrote:
> >>Great to hear about PHP. I hope you don't mind a question. Were you
> >>able to reuse the Python object model for your PHP interpreter, o
On 06/01/2011 06:20 PM, Alex Şuhan wrote:
On 06/01/2011 06:51 PM, Laura Creighton wrote:
Great to hear about PHP. I hope you don't mind a question. Were you
able to reuse the Python object model for your PHP interpreter, or
is the PHP object model too different?
Laura
No, we weren't. We're
On 06/01/2011 05:02 PM, Timothy Baldridge wrote:
We don't particularly care about fibonacci (which is the worst-case
scenario here, recursion works better in cases where functions are
bigger). However there is a plan how to go about it (without
reimplementing the JIT). It's even rela
On Wed, Jun 1, 2011 at 9:33 AM, Dima Tisnek wrote:
> On 1 June 2011 05:14, Alex Şuhan wrote:
> > Hello.
> >
> > PyPy works great for our PHP JIT interpreter, with nice speedups for most
> of
> > the processing-intensive (with loops), shootout-ish scripts. However, I
> feel
> > that short scripts
On 06/01/2011 07:33 PM, Dima Tisnek wrote:
On 1 June 2011 05:14, Alex Şuhan wrote:
Hello.
PyPy works great for our PHP JIT interpreter, with nice speedups for most of
the processing-intensive (with loops), shootout-ish scripts. However, I feel
that short scripts running often could benefit fro
On 1 June 2011 05:14, Alex Şuhan wrote:
> Hello.
>
> PyPy works great for our PHP JIT interpreter, with nice speedups for most of
> the processing-intensive (with loops), shootout-ish scripts. However, I feel
> that short scripts running often could benefit from tracing as well if we
> make the in
On 06/01/2011 06:51 PM, Laura Creighton wrote:
Great to hear about PHP. I hope you don't mind a question. Were you
able to reuse the Python object model for your PHP interpreter, or
is the PHP object model too different?
Laura
No, we weren't. We're reusing the Zend frontend and running (fa
Great to hear about PHP. I hope you don't mind a question. Were you
able to reuse the Python object model for your PHP interpreter, or
is the PHP object model too different?
Laura
___
pypy-dev mailing list
[email protected]
http://mail.python.org/m
On 06/01/2011 05:49 PM, Maciej Fijalkowski wrote:
We don't particularly care about fibonacci (which is the worst-case
scenario here, recursion works better in cases where functions are
bigger). However there is a plan how to go about it (without
reimplementing the JIT). It's even relatively simpl
We don't particularly care about fibonacci (which is the worst-case
> scenario here, recursion works better in cases where functions are
> bigger). However there is a plan how to go about it (without
> reimplementing the JIT). It's even relatively simple. It's just that
> fibonacci wasn't our majo
On Wed, Jun 1, 2011 at 4:36 PM, Alex Şuhan wrote:
> On 06/01/2011 04:05 PM, Armin Rigo wrote:
>>
>> Hi Alex,
>>
>> On Wed, Jun 1, 2011 at 2:14 PM, Alex Şuhan wrote:
>>>
>>> PyPy works great for our PHP JIT interpreter
>>
>> Great to hear :-)
>>
>>> Other than the obvious duct taping, are there an
On 06/01/2011 04:05 PM, Armin Rigo wrote:
Hi Alex,
On Wed, Jun 1, 2011 at 2:14 PM, Alex Şuhan wrote:
PyPy works great for our PHP JIT interpreter
Great to hear :-)
Other than the obvious duct taping, are there any caveats to this solution?
Not that I can think of. It sounds like a good
> PS. I might not be understanding what are your proposed solution
>
Ok, seems I'm slow today. Does sound like a good solution, provided
you clean up the global state in a nice manner.
Cheers,
fijal
___
pypy-dev mailing list
[email protected]
http://m
Hi Alex,
On Wed, Jun 1, 2011 at 2:14 PM, Alex Şuhan wrote:
> PyPy works great for our PHP JIT interpreter
Great to hear :-)
> Other than the obvious duct taping, are there any caveats to this solution?
Not that I can think of. It sounds like a good solution, or let's say
a good workaround, fo
On Wed, Jun 1, 2011 at 2:14 PM, Alex Şuhan wrote:
> Hello.
>
> PyPy works great for our PHP JIT interpreter, with nice speedups for most of
> the processing-intensive (with loops), shootout-ish scripts. However, I feel
> that short scripts running often could benefit from tracing as well if we
> m
Hello.
PyPy works great for our PHP JIT interpreter, with nice speedups for
most of the processing-intensive (with loops), shootout-ish scripts.
However, I feel that short scripts running often could benefit from
tracing as well if we make the interpreter „persistent” -- that is, keep
all the
17 matches
Mail list logo
