Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain toolpark.com from 195.49.42.12 cause and error)
Message-ID: <5035D84D.9000302@toolpark.com>
Date: Thu, 23 Aug 2012 09:14:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <5032A163.9040500@toolpark.com> <2318376F24EC4B76AD4828C7F8E62B46@gmail.com> <50348E10.4050702@lsces.co.uk>
In-Reply-To: <50348E10.4050702@lsces.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Official Userland Library (was: removing an item from
 an array)
From: lars.schultz@toolpark.com (Lars Schultz)

Am 22.08.2012 09:45, schrieb Lester Caine:
> Personally I'm looking for a 'Official Userland Library' that provides
> EXAMPLES of how to do operations rather than yet another downloadable
> library. Something I can cut and past from into my own code when I need
> a widget and which provides a much more 'PHP approved' style to the code
> I'm using now. Putting this into PEAR is most definitely not what I
> need. I need to be able to see the code on-line.

I guess as always, the deployment of this userland-library depends on 
the php-users personal preference. I agree with Lester in that I'd 
rather have it available online as a proven example of how to solve a 
very specific problem instead of loading yet another bunch of functions 
I might not even need, just for the sake of having them.

But I guess we could have both. I am not sure we should have a hefty 
namespace attached to those functions though...it would of course make 
the situation of naming clashes less dire, but that could also be solved 
manually by copy/pasting and then renaming according to taste.

This is the beauty of it all. Wether you want to make the functions 
available globally, grouped as a static class or using namespaces is 
left to the user.

Making the "Library" available for download as a complete package or 
using PEAR/Composer could be a second project, no? Lets focus on how it 
could fit into the manual (or not) and then go on to how it could be 
served as a package?

I'd really like some comments/thoughts from a php-dev on this...and 
maybe someone from docs?