Using c-to-python was remarkably successful. A few notes: The only feature that I might consider adding to c-to-python is translating true to True and false to False. However, this may not always be a safe transformation, and it's easy to do a search and replace.
Happily, differences between C and C++ function declarations made surprisingly little difference in practice. The main transliteration problem is C++'s convention eliding "this->" from members. So one has to remember (from the header files) what all the names of ivars and methods are and "self." in lots of places. There are always nits that have to be transliterated by hand, but they aren't troublesome. The various kinds of local C++ variables required the most munging. It would not be easy to do such munging in c-to-python itself. Such AI was not part of the remit of c-to-python. In short, using c-to-python is much easier than I would have guessed. The process of munging the output gives one a pretty detailed view of the code ;-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
