On Sat, Sep 3, 2016 at 2:53 PM, Rowan Collins
wrote:
> On 03/09/2016 19:44, Lester Caine wrote:
>
>> So this RFC is simply proposing that PHP-FIG becomes the standard for
>> writing PHP code?
>>
>
> No, that is not at all what this RFC is proposing. The RFC is simply
> proposing to stop bundling
On 03/09/2016 19:44, Lester Caine wrote:
So this RFC is simply proposing that PHP-FIG becomes the standard for
writing PHP code?
No, that is not at all what this RFC is proposing. The RFC is simply
proposing to stop bundling the command-line tool "pear" with default PHP
builds.
The PEAR cod
On 9/2/2016 9:32 PM, Davey Shafik wrote:
> Hi internals,
>
> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
> in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+)
> in their place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-composer
>
>
On Sat, Sep 3, 2016 at 4:32 AM, Davey Shafik wrote:
>
> I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
> in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+)
> in their place.
>
> https://wiki.php.net/rfc/deprecate-pear-include-composer
+1
--
Yas
On 03/09/16 16:43, Rowan Collins wrote:
>> This is perhaps my sticking point. I have a perfectly stable framework
>> without the need for any 'autoloader', and a folder structure that
>> works. Reworking the whole framework so that it follows the 'vendor'
>> rules while still also just working with
On 03/09/16 17:11, Rowan Collins wrote:
>> A starting point for a replacement for PEAR might well be a style guide
>> that lays out just how one should build a modern suite of code. My
>> stumbling block deciphering owncloud is just how one does work out
>> exactly what code has been loaded and fro
On 03/09/2016 16:02, Lester Caine wrote:
A starting point for a replacement for PEAR might well be a style guide
that lays out just how one should build a modern suite of code. My
stumbling block deciphering owncloud is just how one does work out
exactly what code has been loaded and from what fi
On 03/09/2016 15:56, Lester Caine wrote:
On 03/09/16 11:20, Rowan Collins wrote:
Interesting, can you give any details of these problems?
https://sourceforge.net/p/tikiwiki/mailman/message/35331374/
Right, so their problem was not with Composer itself, but with Satis,
which is a tool for pub
On 03/09/16 15:45, Rowan Collins wrote:
> - The PEAR coding style would probably be considered "out of date" by a
> lot of PHP devs. That's partly a matter of fashion, but also a natural
> consequence of it predating certain language features - autoloading,
> namespaces, etc - which people want to
On 2 September 2016 at 15:59, Silvio Marijić
wrote:
> Michal I'm talking about __clone() callback after clone operation. But I
> agree with you about syntax part.
>
> 2016-09-02 16:46 GMT+02:00 Michał Brzuchalski <
> michal.brzuchal...@gmail.com>
> :
>
> > 02.09.2016 16:29 "Larry Garfield" napis
On 03/09/16 11:20, Rowan Collins wrote:
> On 3 September 2016 09:18:48 BST, Lester Caine wrote:
>> Is Composer really all there is?
>> I'm looking at the problems projects like tiki have with trying to keep
>> composer working in an active project, and other projects have just as
>> many bug repor
Hey guys :)
# Abstract Classes
Establishing a contract that any child class of an abstract class has to
be immutable is a totally valid use case in my opinion and it aids
consistency. Otherwise we have the same situation as with final which I
never understood. Actually, even interfaces could benef
On 02/09/2016 20:32, Davey Shafik wrote:
I'd like to introduce a new RFC to deprecate pear/pecl (in 7.2, and remove
in 8.0), as well as add composer/pickle (optional in 7.2, default in 7.3+)
in their place.
https://wiki.php.net/rfc/deprecate-pear-include-composer
Hi Davey,
I think this is a s
On 3 September 2016 09:18:48 BST, Lester Caine wrote:
>Is Composer really all there is?
>I'm looking at the problems projects like tiki have with trying to keep
>composer working in an active project, and other projects have just as
>many bug reports of composer having failed again! Keeping the ri
On 02/09/16 20:32, Davey Shafik wrote:
> I'm also proposing voting choices around the optional/default introduction
> of composer/pickle.
Is Composer really all there is?
I'm looking at the problems projects like tiki have with trying to keep
composer working in an active project, and other projec
15 matches
Mail list logo
