Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72124 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41404 invoked from network); 3 Feb 2014 21:15:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2014 21:15:22 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.169 mail-lb0-f169.google.com Received: from [209.85.217.169] ([209.85.217.169:47782] helo=mail-lb0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EE/24-35654-9E600F25 for ; Mon, 03 Feb 2014 16:15:22 -0500 Received: by mail-lb0-f169.google.com with SMTP id q8so5897541lbi.0 for ; Mon, 03 Feb 2014 13:15:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=dUzN0Io4SzEEuQyu/ru1a1xd44+4ujS6Qs4f+j+T8ck=; b=0ubM6obgrozcWJT1zpu2NRaLqCYzRtBrqVt993iHxXG5LcQsZjV7toG1NKThQZk9yh SpzuFXzZ/AmkEPl3A2ezQLVEO5XdpmQV64ebSlV7IrtIjrdGFxepAGYqTqGi/nXcVOIi Og81Om0z7/gcghrcCvEMjFliqXlmKKHahVPL7ERaznttVJ2/TKtPugAKHEWpxVze1NGs ZYVElXtyiznugRSyTDZ6oueajthmcZVC1J8d6lCwO67c3k8kQ0i1u2IvWKZyqUWUKAij TnhpXQdUUClyQxTnhcWPOhss5ozg5PUYSIDEEJIByEqhu3MTTzwel7a14i3JsGJEGG1y nGGg== X-Received: by 10.152.234.36 with SMTP id ub4mr8760835lac.13.1391462118292; Mon, 03 Feb 2014 13:15:18 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Mon, 3 Feb 2014 13:14:37 -0800 (PST) In-Reply-To: <52EF6D4E.8060901@lsces.co.uk> References: <52EE2B1D.7000307@pthreads.org> <52EEA7BE.4050500@sugarcrm.com> <52EEF636.7010505@pthreads.org> <52EF5588.6010902@sugarcrm.com> <52EF6D4E.8060901@lsces.co.uk> Date: Tue, 4 Feb 2014 06:14:37 +0900 X-Google-Sender-Auth: 7H7mVdZkaZJwQ1G645Jr2FqmsPk Message-ID: To: Lester Caine Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11344e5a477fba04f1870521 Subject: Re: [PHP-DEV] RFC: expectations/assertions From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11344e5a477fba04f1870521 Content-Type: text/plain; charset=UTF-8 Hi Lester, On Mon, Feb 3, 2014 at 7:19 PM, Lester Caine wrote: > Yasuo Ohgaki wrote: > >> It is important to remove assertion overheads from production code. >> Therefore, this RFC is valuable people who care about DbC and prefer to >> use >> light weight frameworks like myself. >> > > And when did we agree to support DbC in the core? > It really is feeling as if there are two versions of PHP being developed > ... the one everybody uses and another 'fancy version' with all sorts of > bells and whistles and just a very small minority want. > Why can't all of these extensions simply be supported by third party tools > ... which are already available ... and keep the core as simple as possible. assert() is not new feature, but this RFC is for improving it. Current assert() will call NULL function at run time. Therefore, there would be overheads that cannot be ignored when assert() is used extensively. With this RFC, run time overheads are removed. I agree that this RFC would change the way script is coded. Assertion can be used for DbC, but it's up to users if they use it for DbC or not. No existing code is affected in any way. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11344e5a477fba04f1870521--