Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82700 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62501 invoked from network); 14 Feb 2015 21:01:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Feb 2015 21:01:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.52 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.216.52 mail-qa0-f52.google.com Received: from [209.85.216.52] ([209.85.216.52:58195] helo=mail-qa0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C3/63-41866-997BFD45 for ; Sat, 14 Feb 2015 16:01:14 -0500 Received: by mail-qa0-f52.google.com with SMTP id v10so17215281qac.11 for ; Sat, 14 Feb 2015 13:01:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qlav9VTgycV2X4/yjCVwlN1vuEDKzoBmKkqHZNcRYQw=; b=ATLft6wjD1IkXIdHbCD6g2M7tA8w7m31NacJ7320blwbNqn/vBmGLj5deAVR7SrGpr 1fMx81dkOnTVS7cO9b/rruUvKRbH6tEkuKFiYahSYM1cFfmt1/oKKpADrUbRgvXuZS3G P5d4Qp+U9OPZxfLow9JLMmcVmqkngkvSsvRVNqhrpM4vKbsy5YCqpHP9GADMrZQED5cn UoppeFCHV4qX5c26+dphI2lQrJqOICjNX+bQZjgNK7Z0I+cCzzBDnpcTzbiB7v7dThQS 3MGyMfOLquXxBn+Ne62LuCHFONlCq2Sd+UpbHbst1wM88mJsLUpCSevCxzmajc/w4PjZ WyLQ== X-Received: by 10.140.145.4 with SMTP id 4mr10830319qhr.52.1423947671214; Sat, 14 Feb 2015 13:01:11 -0800 (PST) Received: from Stas-Air.local ([199.168.151.108]) by mx.google.com with ESMTPSA id k3sm10227105qao.0.2015.02.14.13.01.08 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Feb 2015 13:01:10 -0800 (PST) Message-ID: <54DFB790.9080501@gmail.com> Date: Sat, 14 Feb 2015 16:01:04 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Pierre Joye CC: PHP internals , Andrea Faulds References: <680FB44D-B42D-4898-A28B-FA1C6E4D4D1A@ajf.me> <54DEE32B.6040706@gmail.com> <54DF5B79.6050009@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Void Return Type From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > How ignoring values is a perfectly valid scenario? You are saying you're using return value for every function you're calling, always? Please. How many times you used return value of sort()? Every function with side effects can be used for its side effects, not for its return value. > new paradigms. But we must provide features to make php relevant for a > wider audience. And it is possible to do it without making it less easy This sounds like cargo cult, sorry - because other languages have "void", we have to have "void" and then their users would come to us. That's exactly how cargo cult works - copying external appearances without considering underlying processes. In PHP, there's no meaning to void function except for self-enforcing documentation, and documentation should be properly done by other means and should not produce fatal errors. > to use. We had the same discussion about OO when we developed 5.0, see > where we are now. Stronger than ever. No, it's not like OO at all. OO is a huge conceptual framework with very wide use and it can help with developing code and making people more productive. Having "void" just helps with having "void". -- Stas Malyshev smalyshev@gmail.com