Re: Porting ASP code to PHP

From: Date: Mon, 02 Apr 2001 22:10:17 +0000
Subject: Re: Porting ASP code to PHP
References: 1  Groups: php.general 
Request: Send a blank email to php-general+get-46690@lists.php.net to get a copy of this message
And, to get you started (and maybe done in no time flat) in your port, check out this! http://freshmeat.net/projects/asp2php/ No, didn't write, but I used it on a small web app once. Worked like a charm. Your mileage may vary, depending on complexity. But as long as you back up all your code, what could it hurt? On 4/2/01 2:03 PM, "Michael Stearne" <mstearne@entermix.com> wrote: > > The thing that will make PHP look the best right now is to get the > application running in it as soon as possible. If it's quickest to move > the variables to $variables and leave all the business logic how it was > under ASP, then that will help your PHP case the most. Once the code is > simply converted to PHP you will probably see no great increase or > decrease in performance, but the code will be in PHP and you will be > using the "platform". At that point you can start using PHP's abilities > and functions in a better way to continually increase the performance of > the app. If this application was well designed in the first place, it > will run fine in PHP. > > On Monday, April 2, 2001, at 04:37 PM, Mike King wrote: >> >> a) produce a much better application > > The application that is running and showing results to the managers is > the best application. You could write the tightest code in the world, > but if no one can use it, it's not the best. Mozilla is an > extraordinary program, but until people can get a stable version in > their hands, IE continues to gain market share. > > Your PHP app may be amazing when it is finished, but they already had an > ASP version that was finished and performing adequately. This will make > PHP look worse as time goes on. > >> b) take less development time > > If you're starting with a decently designed app already, I can't see how > starting from scratch could be faster. > >> c) cause less bugs > > Maybe, but that's what version 2.0 is for! > >> d) create a more efficient system >> > > Again that can come over time, get it to PHP first and then make it run > better, > > Michael >

« previous php.general (#46690) next »