Re: [pypy-dev] trsnslating pypy to another language besides C

Hi Ryan, On 4 March 2015 at 19:48, Ryan Gonzalez wrote: > Not necessarily. I figured that a C++ target might look a tad nicer because > it has built-in objects and exception handling. Yes, this might be true for the static backend. However, the JIT integration would be extremely painful. To ha

Re: [pypy-dev] trsnslating pypy to another language besides C

Hi Joonas, To make sense out of it, you would need an "ootype" backend, as opposed to a "lltype" backend which generates C-like code. Google for Antonio's thesis "High performance implementation of Python for CLI/.NET with JIT compiler generation for dynamic languages". But we killed support for

Re: [pypy-dev] trsnslating pypy to another language besides C

Nevermind. The link seems dead. On Wed, Mar 4, 2015 at 3:41 PM, Ryan Gonzalez wrote: > I seriously doubt PyPy is going to work well at all under JASS2; it'll > probably be insanely slow. > > This would probably be > better. It's a Python-to-Jass conve

Re: [pypy-dev] trsnslating pypy to another language besides C

I seriously doubt PyPy is going to work well at all under JASS2; it'll probably be insanely slow. This would probably be better. It's a Python-to-Jass converter. On Wed, Mar 4, 2015 at 2:29 PM, Joonas Liik wrote: > the host language is called JASS2*

Re: [pypy-dev] trsnslating pypy to another language besides C

Oh yeah, forgot to mention there are hashtables (in JASS2) that do have infinite storage so .. not quite hopeless.. i hope. :) On 4 March 2015 at 22:29, Joonas Liik wrote: > the host language is called JASS2* > > JASS2 is the underlying scripting language for game basically,(Blizzards > Warcraf

Re: [pypy-dev] trsnslating pypy to another language besides C

the host language is called JASS2* JASS2 is the underlying scripting language for game basically,(Blizzards Warcraft 3 from 2002/2003 depending on where you're from) It is -strongly typed, -not very fast, -supports a grand total of 0 bit-wise operations -it has obscure and arcane w

Re: [pypy-dev] trsnslating pypy to another language besides C

Not necessarily. I figured that a C++ target might look a tad nicer because it has built-in objects and exception handling. Of course, again, it'd likely have its own set of painful holes and would be largely useless. But I still want to try it. ;) On Wed, Mar 4, 2015 at 12:23 PM, Maciej Fijalkow

Re: [pypy-dev] trsnslating pypy to another language besides C

C is C++ right? or what precisely did you want to do? On Wed, Mar 4, 2015 at 8:15 PM, Ryan Gonzalez wrote: > I'd kind of like to know this, too. I've wanted to try to get PyPy to > translate to C++. I doubt it would be of any advantage, but I'm just too > curious... > > On Wed, Mar 4, 2015 at 2:5

Re: [pypy-dev] trsnslating pypy to another language besides C

you need to write a backend. Backends are in translator/xxx. Historically we used to support C, LLVM (to varying degrees), JS, C# (or it's bytecode). What are you targeting? is it low-level enough to make sense? What about the JIT? can you emit assembler and run it? On Wed, Mar 4, 2015 at 10:58 AM

Re: [pypy-dev] trsnslating pypy to another language besides C

I'd kind of like to know this, too. I've wanted to try to get PyPy to translate to C++. I doubt it would be of any advantage, but I'm just too curious... On Wed, Mar 4, 2015 at 2:58 AM, Joonas Liik wrote: > Hey > > If i wanted to translate PyPy in to another language.. > > Where would i start? >

[pypy-dev] trsnslating pypy to another language besides C

Hey If i wanted to translate PyPy in to another language.. Where would i start? What would be the absolute minimum i had to do to get it working? I cant run any C code.. at all (obscure sandboxed platform that only runs an obscure scripting language none of you has probably ever heard of) how m