Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62036
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
MIME-Version: 1.0
Date: Sat, 4 Aug 2012 22:57:49 +0300
Message-ID: <CANVTSm4pseLgp5RnD0Uh5aSvu3Zox6wwu65jDjikTeBXFyySDw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf307ac81f5a272304c676107e
Subject: Integrate PECL into PHP
From: g.b.yahav@gmail.com (Yahav Gindi Bar)

--20cf307ac81f5a272304c676107e
Content-Type: text/plain; charset=ISO-8859-1

Hi,

After the last discussion I've started about runkit which some of you
suggest to keep it in PECL - I thought about the extensions "problem" in
PHP and wish to ask for your opinion.

Many developers use shared hosting as PHP env which not allows them to
install new extensions in PHP.
In order to give users ability to use extensions, I'm suggesting that we'll
add some PECL related methods to the PHP core (with ini option to disable
it, or create a PECL package) that allows users to install PECL packages
through PHP code even in shared hosting env.

We had dl() until it was deprecated, and even when we got it I guess that
administrators disabled the dl() method because of security reasons.
However, PECL got limited extensions which, as long as I know, does not put
the server into security risks (maybe I've said something VERY STUPID right
now, so excuse me...)

Idea example:

<?php

$extensionsList = pecl_get_available_extensions();
if (! pecl_extension_installed('...') ) {
    pecl_install_extension('...');
}

?>

What do you think?

--20cf307ac81f5a272304c676107e--