Re: Re: cvs: php4 / TODO-4.1.txt

At 10:03 PM 4/18/2001 -0400, Stig Sæther Bakken wrote:

["Sean R. Bright" <elixer@erols.com>] To continue a tangent... I don't like the idea of having the PEAR fetching/installation mechanism written in PHP (already some base code in PEAR to do this). It seems to me that it forces the user to download/build PHP and then download and rebuild PHP with any extensions that don't come in the base distribution. Instead it should be a binary that can be compiled before PHP is built, can download and configure any extensions requested and then build the resulting PHP binary. We can also build in a dependency mechanism where for example, someone chooses to install a PEAR module (be it PHP or C) and the required extensions would be downloaded as well. Just my $0.02 I see your point, but personally I code 5 times faster in PHP than in C, and I want to get this done now, not next year. :-) When we're past the prototyping phase and stuff stabilizes, a C rewrite may be a good idea, but I don't think it is now.

Well you know the most permanent things are temporary things such as prototypes. I also thought it would make much more sense to create something very small in C (maybe even Perl as it's installed on all systems) and use that. I'm not really sure anymore what this installer you are talking about looks like. So I think it would be good to get a small update and have a discussion of what we need on php-dev@. Thanks, Andi