Paul attempts to do it using filters in AWK, and aims for an independent program for doing the conversion. Paul's code does it using an AWK script, and clearly mentions not wanting to Octave's parse tree for doing the conversion. A few things are simple to understand, and require plain substituion. The starting point of the program transformation tool would be from Paul Kienzle's work on Now this is double bonanza, a kind of buy-1 and you get-1 free. Using the Octave parser, you could in theory convert Matlab code the other-way The Octave parser is widely acknowledged on our mailing lists as a superset of Matlab It is going to be a long project, but defnitely rewarding one. This is exciting, in terms of the possibilities it opens up for us. I could ' ask' for type inference whenever it is ' confused' by ' ambiguous' nature of the code. Next in a similar spirit of the AST walker static-checker we could also have a program transformation tool for converting Octave -> Matlab code. Its time, I could show the code, instead of waxing eloquent about it. Specifically, flagging unused variables, data type conversions in known stdlibrary of Octave functions and such. Immediately we can think of all the warnings that GCC would spit out, when you compile C/C++ code using ' gcc -Wall '. A few more additional features that could be copied from existing tools in a similar areas.
0 kommentar(er)
