Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45992
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Nov 2009 17:45:20 +0100
Message-ID: <413588E2-8AC8-49F7-B7BF-97BEFB0A71E4@pooteeweet.org>
To: PHP Developers Mailing List <internals@lists.php.net>
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: alternative to the fopen() hack in autoloaders
From: mls@pooteeweet.org (Lukas Kahwe Smith)

Ahoi,

I have written an RFC for a more efficient solution to get rid of the =20=

common fopen() hack inside autoloaders:
if ($fp =3D @fopen($file, 'r', true)) {
fclose($fp);
include $file;
}

Here is the gist of the proposal:
In order to solve the above issues this RFC proposes the addition of a =20=

new construct/function for now called =93autoload_include=94 for lack of =
a =20
better name that largely behaves like the =93include=94 does today with =20=

the following differences, that when the include failed because of a =20
missing file no warning is raised and php null is returned.

Further details can be found on the wiki:
http://wiki.php.net/rfc/autoload_include

As stated in the RFC, I am not happy with the name "autoload_include". =20=

Suggestions welcome!

regards,
Lukas Kahwe Smith
mls@pooteeweet.org