Since we get JSON data, I would also consider $_JSON.
Regards
Thomas
Park Framework wrote on 17.08.2014 01:47:
> Variable $_PUT is already a popular name.
> Many for yourself already so it was called, at the bottom link.
> http://stackoverflow.com/search?q=PHP+%24_PUT
>
> But I like the name $
I think it would be great to have json encoded data from input body in
$_REQUEST, just like parameters from the request-uri or form-urlencoded data.
Regards,
Thomas
Park Framework wrote on 17.08.2014 02:33:
> Maybe, select the best API can community.
> The main thing that it was not a reason fo
Maybe, select the best API can community.
The main thing that it was not a reason for delaying.
2014-08-17 3:25 GMT+03:00 Andrea Faulds :
>
> On 17 Aug 2014, at 00:47, Park Framework wrote:
>
> > Variable $_PUT is already a popular name.
>
> $_POST isn’t really POST data nor is $_GET really GET
On 17 Aug 2014, at 00:47, Park Framework wrote:
> Variable $_PUT is already a popular name.
$_POST isn’t really POST data nor is $_GET really GET data. We shouldn’t
continue this silly naming tradition given both existing names are inaccurate.
We should have a query parameters array and a req
On 17 August 2014 00:51, Andu Aanei wrote:
> Hi,
>
> I am writing this message in order to ask for feedback and advice
> regarding a small feature I wish to implement in the engine.
>
> Currently, when an exception is thrown in a function which has one or
> more string arguments,
> the stack trace
On 17 August 2014 00:47, Park Framework wrote:
> Variable $_PUT is already a popular name.
> Many for yourself already so it was called, at the bottom link.
> http://stackoverflow.com/search?q=PHP+%24_PUT
>
> But I like the name $_DATA - it is universal for any request method.
IMO $_BODY would ma
Hi,
I am writing this message in order to ask for feedback and advice
regarding a small feature I wish to implement in the engine.
Currently, when an exception is thrown in a function which has one or
more string arguments,
the stack trace shows only the first 15 characters of those arguments.
Th
Variable $_PUT is already a popular name.
Many for yourself already so it was called, at the bottom link.
http://stackoverflow.com/search?q=PHP+%24_PUT
But I like the name $_DATA - it is universal for any request method.
For frontend developers, this name is very clear:
$.ajax({
type: "PUT",
This is necessary for convenient use RESTful API.
file_get_contents('php://input') - Very inconvenient
I would like to finally get native support for PHP, preferably version 5.6
> On Aug 16, 2014, at 9:09, Timm Friebe wrote:
> two weeks ago, the RFC `Catchable "Call to a member function bar() on a
> non-object"` was accepted by a vote. I don't have commit access to
> php-src/Zend,
If it's not sorted by someone else, I land this when I get back home later
today.
-Sara
Hi,
two weeks ago, the RFC `Catchable "Call to a member function bar() on a
non-object"` was accepted by a vote. I don't have commit access to php-src/Zend,
so I can't commit this myself. Back from my summer vacation, I thought I'd whip
up this email (after bringing the pull request up-to-date an
On Sat, Aug 16, 2014 at 12:57 PM, Marc Bennewitz wrote:
>
>
> On 15.08.2014 22:39, Andrea Faulds wrote:
>>
>>
>> On 15 Aug 2014, at 19:57, Marc Bennewitz wrote:
>>
>>> Sara,
>>>
>>> shouldn't it be merged into the branches PHP-5.4, PHP-5.5 as well as
>>> PHP-5.6 and shouldn't there an info in the
On 15.08.2014 22:39, Andrea Faulds wrote:
On 15 Aug 2014, at 19:57, Marc Bennewitz wrote:
Sara,
shouldn't it be merged into the branches PHP-5.4, PHP-5.5 as well as
PHP-5.6 and shouldn't there an info in the NEWS file? It's currently
only merged to master.
Marc
There might be an argumen
On Sat, Aug 16, 2014 at 12:22 PM, Aaron Lewis
wrote:
> What should I use in "zend_parse_parameters" so that it can support
> arguments like this:
>
> 1. object, string
> 2. null, string
>
> I'm not sure what represents "null" here
in this case you have to accept a zval and do the check yourself.
What should I use in "zend_parse_parameters" so that it can support
arguments like this:
1. object, string
2. null, string
I'm not sure what represents "null" here
--
Best Regards,
Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371
On 08/16/2014 12:52 AM, Pierre Joye wrote:
On Sat, Aug 16, 2014 at 12:49 AM, David Soria Parra wrote:
On 2014-08-15, Pierre Joye wrote:
Let me summerize a few things that have come up:
(1) phpng doesn't justify PHP7
It does. It's a complete new engine. It has performance improvements
Am 16.08.2014 um 00:19 schrieb David Soria Parra:
> My main concern with this is that it's php6 all over again.
That is my fear, too.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
17 matches
Mail list logo
