Why should a class name contain information that is present in the class
namespace? If you don't like the class name, there is the option to apply a
"use ... as ..." alias.
--
Woody Gilk
http://about.me/shadowhand
On Tue, Oct 4, 2016 at 7:26 PM, Stefano Torresi wrote:
> Il giorno mer 5 ott 2016
Il giorno mer 5 ott 2016 alle ore 01:13 Sara Golemon ha
scritto:
> My $0.02USD is that it should have DI in the name (i.e. DIContainer)
>
100% agree, but I guess this ship has sailed... ;-)
It occurs to my mind that, while most of the development of
container-interop happened outside this list
On Tuesday, October 4, 2016 at 9:40:03 AM UTC-7, Korvin Szanto wrote:
>
> Are you thinking like a text filter PSR or more of an output management
> PSR? It sounds like a single interface with a single method to me:
> `FilterInterface::filter($mixed): mixed;`.
>
>>
>> There's many different forms
On Tuesday, October 4, 2016 at 3:11:26 AM UTC-7, David Négrier wrote:
>
> Actually, the name of the interface was the first issue we discussed when
> starting container-interop (the test-bed for PSR-11).
>
> You can have a look at the Github issue that explains why we ended up with
> ContainerInt
Hi Chris,
Are you thinking like a text filter PSR or more of an output management
PSR? It sounds like a single interface with a single method to me:
`FilterInterface::filter($mixed): mixed;`.
Thanks,
Korvin
On Tue, Oct 4, 2016 at 7:39 AM Chris Riley wrote:
> Hi,
>
> I think there could be quite
Hi,
I think there could be quite some value in producing a spec and set of
interfaces for consistent output escaping across frameworks. Security is an
important consideration in every app and having a consistent API would make
it much easier get it right.
Would like to hear peoples opinions on
PyroCMS remains!
On Sunday, October 2, 2016 at 6:44:02 PM UTC-5, Michael Cullum wrote:
>
> As per the FIG 3.0 bylaws, all member projects must, between the 1st
> October and 31st October, declare they wish to remain a member project of
> the FIG. If you don't wish to remain, then it would be use
Hey Sara,
Actually, the name of the interface was the first issue we discussed when
starting container-interop (the test-bed for PSR-11).
You can have a look at the Github issue that explains why we ended up with
ContainerInterface here:
https://github.com/container-interop/container-interop/i
Revive Adserver remains.
On 03/10/2016 01:43, Michael Cullum wrote:
> As per the FIG 3.0 bylaws, all member projects must, between the 1st
> October and 31st October, declare they wish to remain a member project
> of the FIG. If you don't wish to remain, then it would be useful for you
> to also
Horde remains.
Zitat von Michael Cullum :
As per the FIG 3.0 bylaws, all member projects must, between the 1st
October and 31st October, declare they wish to remain a member
project of the FIG. If you don't wish to remain, then it would be
useful for you to also state this so we don't cha
Stash is out.
Rob
> On Oct 2, 2016, at 4:43 PM, Michael Cullum wrote:
>
> As per the FIG 3.0 bylaws, all member projects must, between the 1st October
> and 31st October, declare they wish to remain a member project of the FIG. If
> you don't wish to remain, then it would be useful for you t
11 matches
Mail list logo
