Hello,
I have a proposal for PHP. The proposed interface would allow developers to decode json into a custom object directly. If given the approval I would possibly be able to implement it.
Here is my github link with further details: https://github.com/decanus/JSON-Aware/tree/master
Regards,
Dean
Hello,
I have a proposal for PHP. The proposed interface would allow
developers to decode json into a custom object directly. If given the
approval I would possibly be able to implement it.Here is my github link with further details:
https://github.com/decanus/JSON-Aware/tree/masterRegards,
Dean
I'll ask before someone else does...
Why does this need to be in PHP core? Why can't it be done purely in
user-space PHP code? The syntax would be different, fine, but how is it
functionally better in C?
--
--Larry Garfield
On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield larry@garfieldtech.com
wrote:
Hello,
I have a proposal for PHP. The proposed interface would allow developers
to decode json into a custom object directly. If given the approval I would
possibly be able to implement it.Here is my github link with further details:
https://github.com/decanus/JSON-Aware/tree/masterRegards,
DeanI'll ask before someone else does...
Why does this need to be in PHP core? Why can't it be done purely in
user-space PHP code? The syntax would be different, fine, but how is it
functionally better in C?--
--Larry Garfield--
PHP already has tons of abstractions designed to provide convenience.
We've never followed the "if it can be done in userland, don't do it in
core" standard. If we did, we would have far fewer array_* functions, for
example.
The question is whether or not this would be useful enough to warrant
putting it in core, not whether or not someone could write a ton of code to
do it in userland.
Dean, could you write an RFC for this proposal? That would make it easier
to evaluate, plus give us something we can vote on.
--Kris
On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield larry@garfieldtech.com
wrote:Hello,
I have a proposal for PHP. The proposed interface would allow developers
to decode json into a custom object directly. If given the approval I would
possibly be able to implement it.Here is my github link with further details:
https://github.com/decanus/JSON-Aware/tree/masterRegards,
DeanI'll ask before someone else does...
Why does this need to be in PHP core? Why can't it be done purely in
user-space PHP code? The syntax would be different, fine, but how is it
functionally better in C?--
--Larry Garfield--
PHP already has tons of abstractions designed to provide convenience.
We've never followed the "if it can be done in userland, don't do it in
core" standard. If we did, we would have far fewer array_* functions, for
example.The question is whether or not this would be useful enough to warrant
putting it in core, not whether or not someone could write a ton of code to
do it in userland.Dean, could you write an RFC for this proposal? That would make it easier
to evaluate, plus give us something we can vote on.--Kris
Except that "this is simple enough to do in PHP, why does it need to be
in core" has been the reason to reject plenty of proposals, too. It's an
entirely fair question to ask, and one that an RFC will need to address.
--Larry Garfield
On Fri, Jul 10, 2015 at 7:07 PM, Larry Garfield larry@garfieldtech.com
wrote:
On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield larry@garfieldtech.com
wrote:Hello,
I have a proposal for PHP. The proposed interface would allow developers
to decode json into a custom object directly. If given the approval I
would
possibly be able to implement it.Here is my github link with further details:
https://github.com/decanus/JSON-Aware/tree/masterRegards,
DeanI'll ask before someone else does...
Why does this need to be in PHP core? Why can't it be done purely in
user-space PHP code? The syntax would be different, fine, but how is it
functionally better in C?--
--Larry Garfield--
PHP already has tons of abstractions designed to provide convenience.
We've never followed the "if it can be done in userland, don't do it in
core" standard. If we did, we would have far fewer array_* functions, for
example.The question is whether or not this would be useful enough to warrant
putting it in core, not whether or not someone could write a ton of code
to
do it in userland.Dean, could you write an RFC for this proposal? That would make it easier
to evaluate, plus give us something we can vote on.--Kris
Except that "this is simple enough to do in PHP, why does it need to be in
core" has been the reason to reject plenty of proposals, too. It's an
entirely fair question to ask, and one that an RFC will need to address.--Larry Garfield
--
Yes I do agree it's a perfectly fair and legitimate question to ask. But I
don't agree that it should ever be the sole reason to reject a proposal
unless the convenience that would be added is insufficient to justify it.
That is, admittedly, a subjective standard, but I believe it's the most
fair.
--Kris
On Fri, Jul 10, 2015 at 7:07 PM, Larry Garfield larry@garfieldtech.com
wrote:On Fri, Jul 10, 2015 at 2:39 PM, Larry Garfield larry@garfieldtech.com
wrote:Hello,
I have a proposal for PHP. The proposed interface would allow developers
to decode json into a custom object directly. If given the approval I
would
possibly be able to implement it.Here is my github link with further details:
https://github.com/decanus/JSON-Aware/tree/masterRegards,
DeanI'll ask before someone else does...
Why does this need to be in PHP core? Why can't it be done purely in
user-space PHP code? The syntax would be different, fine, but how is it
functionally better in C?--
--Larry Garfield--
PHP already has tons of abstractions designed to provide convenience.
We've never followed the "if it can be done in userland, don't do it in
core" standard. If we did, we would have far fewer array_* functions, for
example.The question is whether or not this would be useful enough to warrant
putting it in core, not whether or not someone could write a ton of code
to
do it in userland.Dean, could you write an RFC for this proposal? That would make it easier
to evaluate, plus give us something we can vote on.--Kris
Except that "this is simple enough to do in PHP, why does it need to be in
core" has been the reason to reject plenty of proposals, too. It's an
entirely fair question to ask, and one that an RFC will need to address.--Larry Garfield
--
Yes I do agree it's a perfectly fair and legitimate question to ask. But I
don't agree that it should ever be the sole reason to reject a proposal
unless the convenience that would be added is insufficient to justify it.
That is, admittedly, a subjective standard, but I believe it's the most
fair.--Kris
And where did I ever say or imply that it was the sole reason to reject
a proposal? I asked a question, one that is often asked; nothing more,
nothing less. A question that the OP still hasn't answered, since this
thread has turned into you and I sniping. Good work. You're keeping up
the bad reputation this list has.
--Larry Garfield