Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82093 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9384 invoked from network); 7 Feb 2015 12:12:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Feb 2015 12:12:36 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:58152] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 29/C2-27738-33106D45 for ; Sat, 07 Feb 2015 07:12:35 -0500 Received: (qmail 30797 invoked by uid 89); 7 Feb 2015 12:12:32 -0000 Received: by simscan 1.3.1 ppid: 30791, pid: 30794, t: 0.0692s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 7 Feb 2015 12:12:32 -0000 Message-ID: <54D60130.60902@lsces.co.uk> Date: Sat, 07 Feb 2015 12:12:32 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: PHP Internals References: <54D562CC.3080403@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Pointers to understanding code base From: lester@lsces.co.uk (Lester Caine) Try again ... last attempt just vanished :( On 07/02/15 10:30, Benjamin Eberlei wrote: > I hope this is the right pointer. > > The String API changed completely in ZE3, see the Upgrading docs to PHPNG: > > https://wiki.php.net/phpng-upgrading#strings > > It takes much time wrapping your head around this new way, but I think > in the end its better than before. I've tried to work through that, but > Not all of the extensions code have to be converted to use zend_string instead of char*. It's up to extensions maintainer to decide which type is more suitable in each particular case. does not help if one does not know how one decides ... The main problem is that the smart_string section seems to have an identity crisis? smart_str is till being used in the exmples. Any reaon for that? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk