[wsf-c-dev] Issues for a next generation C stack

[James Clark]

On Wed, 2006-12-06 at 18:11 +0600, Samisa Abeysinghe wrote:
> James Clark wrote:
> > - Use of C++.  Can and should we make use of C++? If so, what
> > restrictions do we need to impose?
> >   
> In case we decide on using C++, what implications would that have on 
> embedding efforts such as PHP extension?

One of the hard requirements on any use of C++ would be that it didn't
cause problems for embedding.  With the right restrictions on C++, I
believe this is possible.  ICU is an existence proof: it's being used as
the basis for PHP6's Unicode support, but it's written mostly in (a
subset of) C++.

> > - Evolution vs revolution.  How do we get from where we are today to
> > where we want to be eventually?  Do we gradually evolve the current
> > code-base or do we start a new code-base?  The technical viability of an
> > evolutionary approach will obviously depend to some extent on the
> > answers to the above questions.
> >   
> In case we choose revolution, what would be the fate of current 
> embedding efforts?

We would need to reimplement the current high-level PHP/Javascript API
on top of the new code-base.  So although it would be work for us, our
current users should be able to switch over without changing their code.

James