This makes me think that the PHP CPAN module is a good thing in this regard, and that frameworks for transition may be better than code converters.
In general rewriting apps in another language means rethinking everything because there are all sorts of things that just don't quite match between apps. Something to ease the transition might be very good. So for example, despite my skepticism I think the following could be helpful
- Boilerplate converters. Take a PHP object definition and turn it into a basic Moo or Moose definition. Don't port the methods, just the boilerplate.
- Bridging type classes. The ability to have a PHP Array inside your Perl code may ease the transition quite a bit.
- Web application frameworks written with conversion in mind.
These strike me as both easier and less work than a full-blown code converter but also provide all the basic infrastructure to allow a human to conversion relatively quickly and easily...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.