Python to C++ Compiler - Just found something neat...

[MoN01]

I just found a new Python to C++ Converter, if anybody would look into this, it would be great.

Here is the Page: http://code.google.com/p/shedskin/

Have fun,
Mon01

[nwru]

Edit: Thread cleaned up, at request of OP.

PLEASE, only post if you have something USEFUL to contribute to the topic. Posts like "OMG COOL" and "yay, now FoF will be on iPhone/PS3/a toaster" will receive warnings.

Thanks.

[gaderael]

This sounds pretty cool, but this quote has me wondering:

Besides the typing restriction, programs cannot freely use the Python standard library (although about 17 common modules, such as random and re, are currently supported). Also, not all Python features, such as nested functions and variable numbers of arguments, are supported

That seems to me that it would put a serious kink in porting FoF over to C++. Unless it allows you to use the C++ equivalents? I'm no coder, but that just popped into my mind. Can anyone correct me or validate what I think? This would be an interesting project.

[Spikehead777]

This looks promising, but with the complications, I would stay with Python. If anything, I would rather rewrite FoF from scratch in C++ than to port the existing code over. There's still quite a few bugs that need to be resolved, and a total rewrite with what has been done already in mind would help a bit.

Also it seems that with the following statement, FoF may not successfully convert over anyways.

Because Shed Skin is still in an early stage of development, however, many other programs will not compile out-of-the-box.

[zackywackyyo]

Wait, if this means you can use python AND C++ you can change and use the server from Strings on Speed for FoF, right? =DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD
People, check for copyrights, and get started please. xD

[R4nd0M]

This isn't as simple as sticking the source code for FOF into the converter and hitting go, compiling and playing. Doesn't work like that. OpenGL and other libraries work differently in C++ than Python, the way programs are structured is also quite different.

This converter has alot of limitations right now. It's much cleaner to start from scratch, but there's no harm in anyone trying.

[jrdnxxhero]

This isn't as simple as sticking the source code for FOF into the converter and hitting go, compiling and playing. Doesn't work like that. OpenGL and other libraries work differently in C++ than Python, the way programs are structured is also quite different.

This converter has alot of limitations right now. It's much cleaner to start from scratch, but there's no harm in anyone trying.

A Fretter knows what he's talking about.

They're limitations to using converters. Especially when converting from source code to source code.

[omfgdrphl]

This looks promising, but won't this mix up the coding a bit? Imagine someone moving everything in your house to different locations. This could mean more new coders, but possible less as well. Again, having a bit of mixed reactions.

[(-X~Maniac.of.Madness~X-)]

I would only take this one seriously
if someone DID care to try and fix some of the coding.
Then we could have a start, a base.
And not just messy, converted Python coding.
[BTW, I think I have no idea what I'm talking about,)
(since I was never a coder.]
After that, I would just hope the project would
reach the awesomeness of the real thing. =)

[R4nd0M]

Alright, I'm having a little play with this and I'll report any findings.

First note: this will only convert .py files to .cpp. It will not touch .pyo bytecode.

[zackywackyyo]

Go R4nd0M!
even if that is lame >_>
(Or is it? Damn my no experience in coding!)

[R4nd0M]

Yeah, I had a look at it. It really is going to be easier to do scratchwork on this. It might be me doing it wrong, though not likely; but I get parsing errors at every turn.

Anyway, this whole thing is going on backburner for a while.