Hello everybody,
for all of you who don’t know, PHP FIG (Framework Interoperability Group,
http://www.php-fig.org/) discusses ways frameworks and libraries can work
together and integrate much easier. Current PSRs are PSR-0 to standardize
autoloading, PSR-1 and PSR-2 that deal with coding style
On Sun, Dec 16, 2012 at 1:02 AM, Lars Strojny wrote:
> Hello everybody,
>
> for all of you who don’t know, PHP FIG (Framework Interoperability Group,
http://www.php-fig.org/) discusses ways frameworks and libraries can work
together and integrate much easier. Current PSRs are PSR-0 to standardize
Hi Kris,
thanks for your response. Just a short note: I'm not in any ways officially
related to PHP FIG, except that I find it personally to be a good initiative.
Rest of the answers below.
Am 16.12.2012 um 11:50 schrieb Kris Craig :
> My one concern with this idea is that it could give the er
hi Lars,
On Sun, Dec 16, 2012 at 10:02 AM, Lars Strojny wrote:
> PHP core currently doesn’t have a vote in that group and I think this is
> something we should change. Is anybody interested in taking part of the
> discussions there and representing PHP core?
My take on this story is more the
Hi Pierre,
Am 16.12.2012 um 13:08 schrieb Pierre Joye :
> This is something we have seen in the past, "legacy" core developers
> were not really in sync with the community needs or wishes. That's why
> we need them to work with the core instead of the other way 'round. It
> will create more bridg
On Tue, 11 Dec 2012, Derick Rethans wrote:
> On Mon, 10 Dec 2012, Herman Radtke wrote:
>
> > Another option is to make an ImmutableDateTime class. The DateTime
> > class could actually be changed to inherit the ImmutableDateTime
> > class. The only extensions on the DateTime class would be the mu
This is so cool, thanks Derick! If you need help with testing or anything else,
let me know.
Am 16.12.2012 um 13:21 schrieb Derick Rethans :
> On Tue, 11 Dec 2012, Derick Rethans wrote:
>
>> On Mon, 10 Dec 2012, Herman Radtke wrote:
>>
>>> Another option is to make an ImmutableDateTime class.
I'm not really against that, but we do need to use the Date namespace -
>>so DateTimeImmutable. It might be trickier to do than it sounds
>>though...
I've started hacking on this - with some luck I'm done before PHP 5.5
beta1.
Am I missing something here?
Isn't this just making the object conte
Lars Strojny wrote:
for all of you who don’t know, PHP FIG (Framework Interoperability
Group,http://www.php-fig.org/) discusses ways frameworks and libraries can work
together and integrate much easier. Current PSRs are PSR-0 to standardize
autoloading, PSR-1 and PSR-2 that deal with coding st
You realize that this is not the list of PHP FIG, right?
On 16 December 2012 15:26, Lester Caine wrote:
> Lars Strojny wrote:
>>
>> for all of you who don’t know, PHP FIG (Framework Interoperability
>> Group,http://www.php-fig.org/) discusses ways frameworks and libraries can
>> work together and
hi Lars,
On Sun, Dec 16, 2012 at 1:20 PM, Lars Strojny wrote:
> Hi Pierre,
>
> Am 16.12.2012 um 13:08 schrieb Pierre Joye :
>
>> This is something we have seen in the past, "legacy" core developers
>> were not really in sync with the community needs or wishes. That's why
>> we need them to work w
Lars,
On Sun, Dec 16, 2012 at 3:26 PM, Lester Caine wrote:
>
Once again this is totally off base. We are not discussing anything
proposed or adopted by the FIG group but how php.net can better
cooperate with this group. I urge you to stay on topic and move any
other topics to the right place.
I have actually started too, but I made it w/o inheritance from DateTime,
and I made many of inline functions to avoid code repetition, so I don't
know how good is it. The code on my work computer, so I can show it
tomorrow.
Derick Rethans писал(а) в своём письме Sun, 16 Dec 2012
16:21:4
Pierre Joye wrote:
On Sun, Dec 16, 2012 at 3:26 PM, Lester Caine wrote:
>
Once again this is totally off base. We are not discussing anything
proposed or adopted by the FIG group but how php.net can better
cooperate with this group. I urge you to stay on topic and move any
other topics to the
On Sun, Dec 16, 2012 at 7:46 PM, Lester Caine wrote:
> Pierre Joye wrote:
>
>> On Sun, Dec 16, 2012 at 3:26 PM, Lester Caine wrote:
>>
>>
>>> >
>>>
>> Once again this is totally off base. We are not discussing anything
>> proposed or adopted by the FIG group but how php.net can better
>> cooper
can we please keep superfluous discussions like coding standards off-list?
I have no issue with representation of fig discussion, but whitespace
discussions have no place on this list...
Anthony
On Dec 16, 2012 2:49 PM, "Paul Dragoonis" wrote:
> On Sun, Dec 16, 2012 at 7:46 PM, Lester Caine wro
Paul Dragoonis wrote:
It's not the only difference that FIG are pushing which is opposite to the
style standards on the core code, so perhaps we should be lobbying them to
come in line with the documented standards?
We done a survey on all the major projects and what their standards
Anthony Ferrara wrote:
can we please keep superfluous discussions like coding standards off-list? I
have no issue with representation of fig discussion, but whitespace discussions
have no place on this list...
The standards being dictated by FIG are at odds with those adopted here for many
yea
On 12/16/2012 12:27 PM, Lester Caine wrote:
> Anthony Ferrara wrote:
>> can we please keep superfluous discussions like coding standards
>> off-list? I
>> have no issue with representation of fig discussion, but whitespace
>> discussions
>> have no place on this list...
>
> The standards being dic
On Sun, 16 Dec 2012, Lester Caine wrote:
> > > I'm not really against that, but we do need to use the Date namespace -
> > > >>so DateTimeImmutable. It might be trickier to do than it sounds
> > > >>though...
> > >
> > > I've started hacking on this - with some luck I'm done before PHP 5.5
> > >
Hi!
> Al the methods will *still* return the modified DateTime object - it's
> just that the one that you *call* f.e. ->modify() on won't change
> anymore.
Doesn't it mean you can just call clone() on it in modifier methods
before doing anything else?
--
Stanislav Malyshev, Software Architect
On Sun, 16 Dec 2012, Stas Malyshev wrote:
> > Al the methods will *still* return the modified DateTime object -
> > it's just that the one that you *call* f.e. ->modify() on won't
> > change anymore.
>
> Doesn't it mean you can just call clone() on it in modifier methods
> before doing anythin
Hi Lars,
Thanks for your detailed response. My thoughts inline below
--Kris
On Sun, Dec 16, 2012 at 3:42 AM, Lars Strojny wrote:
> Hi Kris,
>
> thanks for your response. Just a short note: I'm not in any ways
> officially related to PHP FIG, except that I find it personally to be a
> goo
Rasmus Lerdorf wrote:
On 12/16/2012 12:27 PM, Lester Caine wrote:
Anthony Ferrara wrote:
can we please keep superfluous discussions like coding standards
off-list? I
have no issue with representation of fig discussion, but whitespace
discussions
have no place on this list...
The standards bei
On 12/16/2012 03:20 PM, Lester Caine wrote:
> One gets the impression that it's all too late, so from the other side,
> should all of the core files be changed to follow the new de-facto
> standard? And YES I classify using different white space standards for
> different file formats as more of a
hi,
What does that have to do with the initial question?
It is getting really annoying to see you hi jack every single thread
in this list with totally off topic and lengthy replies. It does not
matter if what the questions raised are important or not, they are off
topic.
We do not, and do not w
On Sun, Dec 16, 2012 at 10:29 PM, Pierre Joye wrote:
> hi,
>
> What does that have to do with the initial question?
>
> It is getting really annoying to see you hi jack every single thread
> in this list with totally off topic and lengthy replies. It does not
> matter if what the questions raised
27 matches
Mail list logo
