Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69705 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63254 invoked from network); 19 Oct 2013 14:43:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Oct 2013 14:43:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=jakub.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=jakub.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.54 as permitted sender) X-PHP-List-Original-Sender: jakub.php@gmail.com X-Host-Fingerprint: 209.85.128.54 mail-qe0-f54.google.com Received: from [209.85.128.54] ([209.85.128.54:53251] helo=mail-qe0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0F/47-23638-48A92625 for ; Sat, 19 Oct 2013 10:43:16 -0400 Received: by mail-qe0-f54.google.com with SMTP id 1so2761184qec.27 for ; Sat, 19 Oct 2013 07:43:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=15SjTWFhGDFWV55vISaNtIWLZMnF7T9nMj+t0T7M+9M=; b=VDPBD2h88b4PgC9L/ppHcNvtqkPHFgUW2c3g8Ph1VXY7YgH5khk2d8UmVV7Xn2twcj JvBQ9hiZfX+DW53dRJLYnbkmJ7VhLyZxISzHeO1kpWD2/F/cuGrHhNRs1tDRdrM7SKk3 um23n4K+toXqWtEleq++9a67XN8LGvBHYaxpTfXgLsFYsX6lWHodKbsAtnGz7TdHY1eq luIT3m7xddwirM9ZVm5twi10Rr1hmr+n+U8xrB3sI3WRiKnsrBKJy1al24AE+IDXOdQU KODRPPFdbOgexhjWrxFPxjcy6WLetX4x396Hrzfuq7WzGoue82kOEqUodNm6gXmF4wcI jQow== MIME-Version: 1.0 X-Received: by 10.49.109.10 with SMTP id ho10mr11121932qeb.84.1382193793419; Sat, 19 Oct 2013 07:43:13 -0700 (PDT) Sender: jakub.php@gmail.com Received: by 10.224.37.133 with HTTP; Sat, 19 Oct 2013 07:43:13 -0700 (PDT) In-Reply-To: <3D.BC.23638.84CA1625@pb1.pair.com> References: <3D.BC.23638.84CA1625@pb1.pair.com> Date: Sat, 19 Oct 2013 15:43:13 +0100 X-Google-Sender-Auth: _rqaQ05zUDZCzQ_3ppJ68Ck___Y Message-ID: To: Joe Watkins Cc: PHP internals list Content-Type: multipart/alternative; boundary=047d7bdca488114dea04e91912b2 Subject: Re: [PHP-DEV] RFC: Expectations From: bukka@php.net (Jakub Zelenka) --047d7bdca488114dea04e91912b2 Content-Type: text/plain; charset=ISO-8859-1 Hi, On Fri, Oct 18, 2013 at 10:46 PM, Joe Watkins wrote: > Evening Chaps, > > Following on from discussion regarding assertion API in PHP, the > following RFC is now up for discussion: > > https://wiki.php.net/rfc/**expectations > > Please do point out any missing sections or information, so that > it can be clarified as quickly as possible. > > I hope this conveys the idea a bit clearer to everyone ? > > Cheers > Joe I think it's a nice idea. However I am not so sure if it's worthy introducing a new keyword 'except' which will break all existing code where except is used as a function name, class name... Could it be actually mentioned in the RFC that there is a new keyword? It's quite clear from the examples but it would be nice if it could be specified as it's quite important IMHO. In addition I have got more technical question about using ext functions in engine. I saw that you used php_trim in zend_compile.c. Is it a good idea to do that? Wouldn't be better to create a new function (for example zend_str_trim) in the engine (zend_operator.c comes to my mind as it contains zend_str_tolower and other similar function) and then use this function by php_trim? Jakub --047d7bdca488114dea04e91912b2--