Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80119
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.40 cause and error)
Message-ID: <54A7CCEC.7080105@fischer.name>
Date: Sat, 03 Jan 2015 12:05:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <41D5BB0B-73AF-488E-968D-90B2878E3178@ajf.me> <CAEZPtU79=VX1Scm6vVn-9iuHD=qqRoPMrsR4Ymqd9=QQeQbRCg@mail.gmail.com>
In-Reply-To: <CAEZPtU79=VX1Scm6vVn-9iuHD=qqRoPMrsR4Ymqd9=QQeQbRCg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Spam_score: -2.9
X-Spam_score_int: -28
X-Spam_bar: --
X-Spam_report: Spam detection software, running on the system "scanner01.home", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 the administrator of that system for details.
 
 Content preview:  On 03.01.2015 05:50, Pierre Joye wrote: > I am also not a
   fan of errors, exception, at least for methods, make > much more sense. I
   know it is relatively easy to handle errors as > exception but still, let
   do it right now. [...] 
 
 Content analysis details:   (-2.9 points, 5.0 required)
 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP
 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                             [score: 0.0000]
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints
From: markus@fischer.name (Markus Fischer)

On 03.01.2015 05:50, Pierre Joye wrote:
> I am also not a fan of errors, exception, at least for methods, make
> much more sense. I know it is relatively easy to handle errors as
> exception but still, let do it right now.

I second this; this could be an excellent opportunity into that
direction favored by many developers here (judging by the number of
times this and related "exception" topics come up on the list) but yet
we lacked the "how to start"/"how to get it right" approach and this
could be the gradual start of the shift.

thanks for bringing this up,
- Markus