Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69564
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.73.107 as permitted sender)
To: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 15 Oct 2013 17:16:26 +0200
Message-ID: <1381850186.29722.372.camel@ghost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Core extension versions
From: ab@php.net (Anatol Belski)

Hi,

as part of the extension version check on PECL it turned out, that the
extensions in the core are almost completely out of track with their
versions, not even to talk about version macros names. That regards to
exts imported from PECL as well as to the exts never been in PECL. Here
are a few examples of zend_module_entry version strings:

ext/simplexml
"0.1"

ext/bz2
NO_VERSION_YET (== NULL) but was PECL 1.0 in 2003

ext/pdo
"1.0.4dev" whereby it was PECL 1.0.3 in 2006

and the winner might be that from ext/tokenizer

"0.1", /* Replace with version number for your extension */

as if it were just generated :)

Only a few extensions, just to name some - zip, dom, oci8, track the
version number.

Actually that doesn't look solid for the extensions being in the core
for years. And while that's a minor issue, it doesn't really smell good.
So, do we wanna do something about it?

Regards

Anatol