Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69656
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CABXB=RRtknQBYqhnD=uieOX-LCw2CHcXNK3_pqsj2e39g-WBmQ@mail.gmail.com>
References: <D7.A0.22512.AE09F525@pb1.pair.com>
	<525FC834.4060501@php.net>
	<CAMUwpuRHpAB6ut8CZ2TJJF0oJJ7B1QfSP_+Nfv3sda=QoyWb-A@mail.gmail.com>
	<1534105.bNC2os93J1@rofl>
	<CALJZF3h75yw2=mETjyZz1=005XmwX1K2wHujfRMufu3QBL_rrg@mail.gmail.com>
	<525FDAC3.6060103@php.net>
	<CABXB=RTU=m-Ugkkk1gqa_HXRV_K7dPL3CEuyzDtY+EwQ8mD=aw@mail.gmail.com>
	<CAF+90c-s-tanQoYV+AzkjxWJ_crJPPxT4HJg4dfnaFMfx5i4gA@mail.gmail.com>
	<526023DF.6080203@ajf.me>
	<CABXB=RRtknQBYqhnD=uieOX-LCw2CHcXNK3_pqsj2e39g-WBmQ@mail.gmail.com>
Date: Thu, 17 Oct 2013 21:25:42 +0200
Message-ID: <CAF+90c8uFTC=p65jtHHCGy9vFbPQS-5UpemzYnpRPt5kF=5ApA@mail.gmail.com>
To: J David <j.david.lists@gmail.com>
Cc: Andrea Faulds <ajf@ajf.me>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01634ec2a60f8504e8f4c8c5
Subject: Re: [PHP-DEV] Assertions
From: nikita.ppv@gmail.com (Nikita Popov)

--089e01634ec2a60f8504e8f4c8c5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 17, 2013 at 8:16 PM, J David <j.david.lists@gmail.com> wrote:

> On Thu, Oct 17, 2013 at 1:52 PM, Andrea Faulds <ajf@ajf.me> wrote:
> > In addition to all that you've said, I should point out that both Java
> and
> > Python have an assert statement which raises an exception, which happen=
s
> to
> > be called AssertionError in both languages.
>
> And in Python you can subclass an int.  This does not make that a good
> idea for PHP.  (Java only wishes it could subclass int, hence
> Integer.)
>
> In Java, for better or for worse, every error is an exception.  This
> does not make that a good idea for PHP.
>
> (Shrill voice) "If all your friends jumped off a bridge=85"
>

Well, I'd ask myself *why* they all jumped. Since they are not dumb,
there's likely a good reason for it. Maybe it's a wooden bridge and it's on
fire? In that case, sure, I'd jump right after them ;)


> Should require($myFile) throw an exception too?  (Some people, perhaps
> many, would say yes.)  What about parse errors in a file include()d at
> runtime?
>

Yes, require() should throw an exception from a modern point of view. It
doesn't, because it was introduced at a time where we had no exceptions.
Parse errors should theoretically also be exceptions, but with the current
compiler this is simply technically infeasible. Actually "technical
infeasibility" is the only sane reason I can think of to throw a fatal
error.

Anyway, I won't continue this pointless discussion, doesn't seem like we're
getting anywhere with it.

Nikita

--089e01634ec2a60f8504e8f4c8c5--