On 6/3/2017 6:40 PM, Fleshgrinder wrote:
> Next promised RFC (and the last one for this weekend):
>
> https://wiki.php.net/rfc/namespaces-in-core
>
> I am unsure about whether we should avoid the usage of abbreviations for
> things like language (lang), standard (std), and utility (util). I think
On 6/3/2017 6:40 PM, Fleshgrinder wrote:
> Next promised RFC (and the last one for this weekend):
>
> https://wiki.php.net/rfc/namespaces-in-core
>
> I am unsure about whether we should avoid the usage of abbreviations for
> things like language (lang), standard (std), and utility (util). I think
On 6/11/2017 1:08 AM, Dan Ackroyd wrote:
> Hi 'Fleshgrinder',
>
> I object to this RFC on principle.
>
> RFC's are supposed to be opionated. They are supposed to present an
> argument for why we should do something, and why doing that is a good
> idea.
>
> This RFC does not do that; it presents
Hi 'Fleshgrinder',
I object to this RFC on principle.
RFC's are supposed to be opionated. They are supposed to present an
argument for why we should do something, and why doing that is a good
idea.
This RFC does not do that; it presents a series of questions to vote
on, without any clear present
On 6/10/2017 11:11 PM, Levi Morrison wrote:
> You put out namespaces for them which implies you think we might do that.
>
Erm ... not really ... I am sorry if my examples lead to a confusion on
your side.
Let's try this the other way around. What are *other extensions* for you?
--
Richard "Fle
On Sat, Jun 10, 2017 at 1:34 PM, Fleshgrinder wrote:
> On 6/10/2017 9:24 PM, Levi Morrison wrote:
>> If we were starting from scratch maybe we'd do as you are proposing.
>> However, there is absolutely zero value in these specific things being
>> namespaced *anywhere*:
>>
>> - Arrays
>> - Refl
On 6/10/2017 9:24 PM, Levi Morrison wrote:
> If we were starting from scratch maybe we'd do as you are proposing.
> However, there is absolutely zero value in these specific things being
> namespaced *anywhere*:
>
> - Arrays
> - Reflection
> - Strings
> - IO
>
> We already have establishe
On Sat, Jun 10, 2017 at 1:13 PM, Fleshgrinder wrote:
> On 6/10/2017 8:54 PM, Levi Morrison wrote:
>> I gave this feedback before but I'll repeat it. I support namespaces
>> in the core, with the `PHP` namespace (with whatever capitalization we
>> decide) to be reserved *solely* for things related
On 6/10/2017 8:54 PM, Levi Morrison wrote:
> I gave this feedback before but I'll repeat it. I support namespaces
> in the core, with the `PHP` namespace (with whatever capitalization we
> decide) to be reserved *solely* for things related to the language
> itself such as lexer, parser, etc.
>
> I
On Sat, Jun 10, 2017 at 12:11 PM, Fleshgrinder wrote:
> On 6/3/2017 6:40 PM, Fleshgrinder wrote:
>> Next promised RFC (and the last one for this weekend):
>>
>> https://wiki.php.net/rfc/namespaces-in-core
>>
>> I am unsure about whether we should avoid the usage of abbreviations for
>> things like
On 6/3/2017 6:40 PM, Fleshgrinder wrote:
> Next promised RFC (and the last one for this weekend):
>
> https://wiki.php.net/rfc/namespaces-in-core
>
> I am unsure about whether we should avoid the usage of abbreviations for
> things like language (lang), standard (std), and utility (util). I think
Next promised RFC (and the last one for this weekend):
https://wiki.php.net/rfc/namespaces-in-core
I am unsure about whether we should avoid the usage of abbreviations for
things like language (lang), standard (std), and utility (util). I think
it is not necessary to write them out fully, but, we
12 matches
Mail list logo
