I'm often needing to collaborate or interoperate with Matlab
users.  Eventually, I would like to see the ability to call PDL
routines from Matlab and vice-versa.  In the near term, a
M-file import wizard might be more implementable.

The idea is to import an M-file, parse and convert what
we can do correctly (in theory, we could compile to PDL
completely), and provide stubs for any missing or
untranslated functions.  The hope would be to produce
a .pdl file version that will compile (if not run).

Initial functionality:
- convert loop constructs
- identify variables and add $ to the names
- convert index limits
- generate function stubs to be filled in
- fix limits on dimensions

Just having the first few items addressed would be a
big help in reducing the effort and possible errors in
.m <-> .pdl file conversions.  It might make sense to
have an import plugin for Padre as well.

Thoughts?
Chris
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to