On Sep 20, 6:16 am, "Edward K. Ream" <[email protected]> wrote:
> Suppose c-to-python produces wildly incorrect results. As you say, this is > to be expected. One reason I'm not too concerned about the correctness of the code that c-to-python produces is that we expect much of the "Pythonized" C code to go away :-) This is my real objection to C. It's not that C code is hard to write. It isn't. It's that C programmers end up doing endless things in order to get around the feebleness of the language. Sometimes the effort is essential, but for a program like swig there is no reason not to use Python's true power. For example, I haven't studied swig's DOH library in detail, but it's hard to imagine an "object" library surviving a translation to Python. But maybe there is more there than meets the eye at first glance... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
