Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72717
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: "Ivan Enderlin @ Hoa" <ivan.enderlin@hoa-project.net>
Cc: internals@lists.php.net
In-Reply-To: <530623CD.7010605@hoa-project.net>
References:
	 <CAEZPtU4zzN=Xxs03XbBGEM2UTVe3jXH5TAaXUqjsVkzm3kOOyg@mail.gmail.com>
	 <53061982.2050901@googlemail.com>
	 <CAEZPtU5qnhwcq1BCkqG99dXJ8F=p6K8ABALacCiAOvPBQ=huYQ@mail.gmail.com>
	 <530623CD.7010605@hoa-project.net>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 20 Feb 2014 17:25:44 +0100
Message-ID: <1392913544.3990.847.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [php6] Unicode support, options?
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Thu, 2014-02-20 at 16:48 +0100, Ivan Enderlin @ Hoa wrote:
> Hello :-),
> 
> 
> On 20/02/2014 16:44, Pierre Joye wrote:
> > Also pure c++ api is not an option yet. Unless we rewrite php in c++ but
> > then I would go with a 3-4 years Dev phase, not really what I am looking
> > for.
> Several projects use a mix of C and C++ (the first name that comes in my 
> minds is Gecko). That's not a bad thing.

Mixing to some degree is fine. The issue here is that essentially all
our source files become C++ files as basically everywhere we need string
APIs ... ok, we might abstract away most common things behind C wrappers
but then we get a fancy mix where we can't use the good parts of C++ but
are bound by C's limitations.

Not really good for having maintainable clean code. Pure C++11 could
bring nice code (with some C++ weirdness) but that's a rewrite, not an
evolution. (-> HHVM). In PHP's context C++ is good to use in individual
libraries (i.e. ext/intl) but not for core foundation things.
Unfortunately.

johannes