Additionally, return type hinting could strengthen the use of interfaces.
That could problems with implementing interfaces (or an API) from having
to do checking to ensure a method in a class implementing an interface
is behaving as it should (returning the right stuff).
On 2/28/2012 12:35
Now hold on a sec - It's ok to vote to determine the fate of PHP
development - for the entire PHP-lovin' world.
Yet, it's not ok to vote for the handful of developers to collaborate?
Three weeks of discussion (based on what I've seen here on the list)
seems not enough for such a heavy change.
On 8/14/2011 3:42 PM, Lester Caine wrote:
Gwynne Raskind wrote:
The only real disadvantage to hg is having to handle python code to
maintain
> it, people might start converting from PHP;) Although phphgadmin is
a start
> to improving the php interface support and could be a good start at
a fully
GitHub (and Bitbucket) have made forking a social endeavour - it's meant
to be a noisy space of code forks for collaboration just as Stas mentioned.
Bottom line: *if* a DVCS is adopted - enhancing policies and a process
that supports little additional burden on maintainers is required.
Having
I've sifted through the RFC for the array shorthand changes which are
quite nice. Something I'm sure has been brought up, but possibly not
recently: shorthand array splice. Has there been any notion to the
introduction of this feature in the future?
The reason I bring this up is it seems that
Are there changelogs available without downloading?
I keep digging but can't find one - only for standard releases
(http://www.php.net/ChangeLog-5.php#5.2.11)
>>> On 10/20/2009 at 17:31, Johannes Schlüter
wrote:
The second release candidate of 5.3.1 was just released for testing
and can be d
