Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85682
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.46 as permitted sender)
Message-ID: <551C8F18.7080401@gmail.com>
Date: Wed, 01 Apr 2015 17:36:40 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Christoph Becker <cmbecker69@gmx.de>, 
 Dennis Birkholz <dennis@birkholz.biz>,
 internals@lists.php.net
References: <CAH-PCH74+2-S2ySME1X5QW5rA9Jb5=1T+hJ3t1sxHiaTO31RJA@mail.gmail.com> <551BC7CF.3080309@birkholz.biz> <551C44C7.6060108@gmail.com> <551C48AC.3090908@birkholz.biz> <551C4A60.2050805@gmail.com> <551C5045.3010405@birkholz.biz> <551C56E2.8090100@gmail.com> <551C5AFB.7090107@birkholz.biz> <551C6296.40101@gmail.com> <551C7B32.70200@gmx.de> <551C7D86.6040608@gmail.com> <551C8B8C.4050206@gmx.de>
In-Reply-To: <551C8B8C.4050206@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] What's our official stance on small self-containedadditionsin
 a micro version
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> But what is "properly prefixed"?  Is there a list of reserved prefixes?

Yes, it's called the manual :)

> I agree.  However, there are other "namespaces" which are not so
> special, especially for beginners, for instance, array_* and str_*.  And

Adding something like strlen() in core now probably would be dangerous.
array_* OTOH should be obvious as reserved. Just follow common sense -
if you prefix your function the same way as a function group in the
manual, then you're in trouble.

> of course, someone might consider it to be reasonable to invent a new
> function in userland which is an extension of some existing function,
> therefore giving it a similar name, e.g. preg_replace_callback_array().

Someone would be wrong then.

>  Would that be considered to be bad style?  If so, where is it documented?

Yes. It is common sense. Not everything has to be spelled out to be
true, and I think rule lawyering and ignoring common sense is not going
to help anybody here. If you don't understand that adding preg_*
function in global namespace that looks like existing core function is a
bad idea, maybe some mentorship by more experienced developer is in order.

> I'm aware that I'm nit-picking, and that the probability of such
> collisions is near zero, but it is not equal to zero.

If we limit ourselves only to changes that have exactly zero chance of
affecting somebody's work however weird and broken that is, we may as
well pack our things and go home, because we'd never do anything at all.
I'm feeling that I am arguing with more and more bizzare scenarios
invented for the purpose to arrive at predetermined conclusion instead
of determining conclusion by real scenarios that sane developers do.
-- 
Stas Malyshev
smalyshev@gmail.com