Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78906
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
In-Reply-To: <CAKd8ng_TAR_warkH7soM7vx3uny_gHK0eZ4pCO3jRMnO4uXr4Q@mail.gmail.com>
Date: Fri, 14 Nov 2014 11:32:27 +0000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <2D612216-1942-47F3-A84D-7301BB1A4CB8@ajf.me>
References: <CAKd8ng_TAR_warkH7soM7vx3uny_gHK0eZ4pCO3jRMnO4uXr4Q@mail.gmail.com>
To: "Mathieu D." <mathieudmeyer@gmail.com>
Subject: Re: [PHP-DEV] Extend bundled exceptions
From: ajf@ajf.me (Andrea Faulds)


> On 14 Nov 2014, at 07:39, Mathieu D. <mathieudmeyer@gmail.com> wrote:
>=20
> PHP is lacking of some elemental exceptions. One obvious example would =
be
> FileNotFoundException.
>=20
> Java has a FileNotFoundException,
> C# has a FileNotFoundException,
> Python has a FileNotFoundError, ...
>=20
> Why doesn't PHP provide a bundled FileNotFoundException or at least a =
more
> general IOException?

Presumably this is because most of PHP=E2=80=99s I/O stuff still uses =
procedural APIs with error return values.

One of the things I=E2=80=99d like to see happen, but don=E2=80=99t have =
the time to do myself, is get rid of the IS_RESOURCE type from PHP for =
PHP 7, and replace all instances with objects. As part of this, we=E2=80=99=
d need to convert streams to using objects, which would give us an =
opportunity to create a new OOP stream API, learning from our past =
mistakes and which uses exceptions. As part of that, I=E2=80=99m sure =
we=E2=80=99d add some I/O exceptions.

--
Andrea Faulds
http://ajf.me/