Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-20 Thread Stig Sæther Bakken
[Andi Gutmans <[EMAIL PROTECTED]>] > At 08:13 AM 4/19/2001 -0400, Stig Sæther Bakken wrote: > > > >To be quite blunt, I don't have the time to implement this in C. > > > >I've tried to get people involved in the strategy for PEAR for months > >and months. It's typical that nobody reacts until aft

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-19 Thread Jason Greene
> I still think that a large majority of people will want to grab the > C-extensions and compile them statically into PHP, i.e. putting them in > ext/, ./buildconf, ./configure ... > > Andi I agree. There is also the possibility that some extensions will have problems as a .so on some archetec

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-19 Thread Andi Gutmans
At 09:05 AM 4/19/2001 +0300, Alexander Bokovoy wrote: >On Thu, Apr 19, 2001 at 07:21:32AM +0200, Andi Gutmans wrote: > > At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > > > >When we're past the prototyping phase and stuff stabilizes, a C > > > > >rewrite may be a good idea, but I don't thin

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-19 Thread Andi Gutmans
At 08:13 AM 4/19/2001 -0400, Stig Sæther Bakken wrote: >[Andi Gutmans <[EMAIL PROTECTED]>] > > > > Right but if we chose XML this makes it much harder to have C clients > > (even Perl because the module might not be installed). I don't think > > >Over my dead body. Take a look at all

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-19 Thread Stig Sæther Bakken
[Andi Gutmans <[EMAIL PROTECTED]>] > > Right but if we chose XML this makes it much harder to have C clients > (even Perl because the module might not be installed). I don't think Over my dead body. Take a look at all the magazines reviewing which web development tools to use. Mos

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4/ TODO-4.1.txt

2001-04-18 Thread Derick Rethans
On Thu, 19 Apr 2001, Andi Gutmans wrote: > 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. PERL isn't installed

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-18 Thread Alexander Bokovoy
On Thu, Apr 19, 2001 at 07:21:32AM +0200, Andi Gutmans wrote: > At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > > >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 thi

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4/ TODO-4.1.txt

2001-04-18 Thread Rasmus Lerdorf
> >If we were to write it in C we would most likely need to provide a > >statically linked binary anyway for the different platforms as not > >everyone will have access to a fully functioning development environment. > > If they are compiling PHP and PHP extensions we can expect them to be able >

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-18 Thread Andi Gutmans
At 09:24 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > > > >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 thin

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4/ TODO-4.1.txt

2001-04-18 Thread Rasmus Lerdorf
> At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > > >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 als

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-18 Thread Andi Gutmans
At 09:16 PM 4/18/2001 -0700, Rasmus Lerdorf wrote: > > >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 w

Re: [PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4/ TODO-4.1.txt

2001-04-18 Thread Rasmus Lerdorf
> >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

[PHP-DEV] Re: [PHP-CVS] Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 / TODO-4.1.txt

2001-04-18 Thread Andi Gutmans
At 10:03 PM 4/18/2001 -0400, Stig Sæther Bakken wrote: >["Sean R. Bright" <[EMAIL PROTECTED]>] > > 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 th