Hi Bjorn, I think the best approach is highly-dependent to your current C application design and "way of doing things". For a type of application you would take the opposite path than for other I thought.
Yes I did that one time, but I re-coded all from scratch... and since that I usually do in reverse: code in Python, then optimize if needed in C via pyrex coded extensions and glue. If you don't know well the current application internals, both approaches can be harder: to convert step by step to python or re-implement from scratch. You need to know well what is doing there that pretty hard to read code for being sure for success and good starting guidelines. I thought If your app doesn't have very critical parts, and if you really know what the application is doing "inside", I would bet for a complete reimplementation from scratch. More if you say current C code has a lots of bugs! And all the code you need to be in C, can be easily done via pyrex, ctypes, etc. Have in mind I don't know your application! Swig is harder, is more suited to export whole libraries to between languages. Anyway, I'm no expert with Swig! :-) Regards, Gonzalo Monzón. -- http://mail.python.org/mailman/listinfo/python-list