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 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@.
> > >
> > >I see no issue with writing a prototype in PHP.  The start of such a
> > >prototype is in cvs (pear/script/pear)
> > >
> > >And yes, using XML is pretty much a no-brainer here.  That will allow a
> > >lot of different nifty tools to access the package information.
> >
> > For a start you don't have PHP installed on most systems. So PHP would 
> need
> > to compile itself and then fetch packages and recompile itself. Seems 
> to me
> > like the no-brainer isn't such a no-brainer.
>Seems that you're forgetting main point of PEAR: you don't need to
>recompile PHP itself when adding some module via PEAR because more
>suitable method exists -- self contained extensions -- which works via
>PEAR right now. Of course, there is small number of extensions from /ext
>which could be compiled in this mode out-of-the-box right now (mostly
>because building environment in PEAR still unreliable), but it exists.

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


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to