in reply to Poetry in the Machine

framboise:

Why are you tempted to rewrite it in perl? Don't get me wrong--I *love* perl. But I hate to rewrite anything when I have it already written.

I don't remember much PHP (it's been about 7 years, so anything I remembered would be out of date anyway), so I don't know what benefits you'd gain. But all languages have a few potholes here and there. So when you rewrite it, unless you're going to rearchitect bits of it as you go, you'll find out that you'll have to dodge a few perl potholes, and your code would be littered with the remains of translated PHP potholes. That (and the time investment) would probably offset any gains perl might give you.

Just askin'.....

...roboticus

Replies are listed 'Best First'.
Re^2: Poetry in the Machine
by framboise (Novice) on Oct 08, 2007 at 05:01 UTC
    Most of the work that I've put into the project has been research and databasing, so the PHP I've written isn't so extensive that it would be incredibly hard to rewrite, and most of it will need revision as I try to incorporate it into a larger system.

    Perl is more dynamic than the PHP that's locked up in my server and from what I've read can probably be integrated more easily into other systems. This might actually become more of an issue later if I work with systemic grammars. Perl modules will allow me to cut some corners, and I'm all for that. I already see that there are some modules that do almost exactly what my stuff does. Lastly, although it at first didn't seem like much of a factor, the Perl community is more centralized and geared towards this type of work. I found very little documentation on NPL+PHP, because that's just not what PHP is about.