Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82685
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain phcomp.co.uk designates 78.32.209.33 as permitted sender)
Date: Sat, 14 Feb 2015 13:07:47 +0000
To: internals@lists.php.net
Message-ID: <20150214130747.GV22130@phcomp.co.uk>
Mail-Followup-To: internals@lists.php.net
References: <680FB44D-B42D-4898-A28B-FA1C6E4D4D1A@ajf.me>
 <012c01d04812$bf8e7560$3eab6020$@php.net>
 <0E369BA2-363A-4AF5-88F2-3643CCE55E5C@ajf.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0E369BA2-363A-4AF5-88F2-3643CCE55E5C@ajf.me>
Organization: Parliament Hill Computers Ltd
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [PHP-DEV] [RFC] Void Return Type
From: addw@phcomp.co.uk (Alain Williams)

On Sat, Feb 14, 2015 at 12:26:08PM +0000, Andrea Faulds wrote:

> We could do this, but for the longest time we've made all functions have some return value, even ones which don't explicitly return one (they return NULL). I think it'd be better not to change this. I expect IDEs and such could earn you about it, though.

All *existing* functions have a return value. That would not change.

If someone makes one of their functions void then where they use it could not be
where a value is needed. So: expect it in new code; but in 5 years time that
code will be mature.

-- 
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256  http://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php
#include <std_disclaimer.h>