>Good point. That's what i meant by border-line case. Could you possibly
>
>point me to a specific example of such false positive? I'm interested
>in
>well-formed UTF-8 string. I believe "noël" test is ill-formed UTF-8
>and
>doesn't conform to shortest-form requirement.
You're confusing two co
Hi Chris,
On Tue, October 14, 2014 15:35, Chris Tankersley wrote:
> Hello all.
>
>
> Partially fueled by a joke to get PHP to compile on Windows 10, and
> partially fueled by starting to look more into core, I found some issues
> with the javascript-based configuration under Windows 10 and Visual
On Wed, Oct 15, 2014 at 2:39 AM, Rasmus Lerdorf wrote:
> On 10/14/2014 05:20 PM, Tjerk Meesters wrote:
>>
>> On 15 Oct 2014, at 01:24, Rasmus Lerdorf wrote:
>>
>>> On 10/14/2014 10:14 AM, Stas Malyshev wrote:
Hi!
> IMO, AST, INT64, NG, Uniforme variables style is enough for a new
>
On Tue, Oct 14, 2014 at 4:00 PM, Johannes Schlüter
wrote:
> On Mon, 2014-10-13 at 23:06 -0700, Stas Malyshev wrote:
>> - drop incompatible $this context calls (probably seriously messed up
>> code)
>
> Before removing: Could anybody check whether this breaks PEAR (incl.
> `pecl install`) I don't k
Hi Chris,
I've just blogged about IDN support in PHP. This post include a (tiny)
userland implementation of streams:
http://dunglas.fr/2014/10/internationalized-domain-name-idn-and-php/
What do you think about the following to add native support :
1. As already stated, make ICU a dependency of co
On 15/10/14 10:04, Rowan Collins wrote:
Rowan,
As I said at the top of my first post, the important thing is to capture
what those requirements actually are. Just as you'd choose what array
functions were needed if you were adding "array support" to a language.
I'm sorry for not making mysel
If we aren't able to fix a low-level problem in a year we most probably
won't be able to fix it in two as well.
Also, the closer we are to release, the more feedback we get, and the more
bugs are able to fix.
Delaying release would just reduce the attention of the users.
Thanks. Dmitry.
On Tue,
Aleksey Tulinov wrote (on 15/10/2014):
On 15/10/14 10:04, Rowan Collins wrote:
Rowan,
As I said at the top of my first post, the important thing is to capture
what those requirements actually are. Just as you'd choose what array
functions were needed if you were adding "array support" to a lan
2014-10-15 4:30 GMT+03:00 Stas Malyshev :
> Hi!
>
>> PHP today to enable successful & easy implementation of RESTful
> interfaces.
>
> Having done this, I beg to differ.
>
>> Try to send a parameter in the body, by PUT method, for reading
>> parameters have to use an ugly way file_get_contents(‘php
On 15/10/14 15:58, Rowan Collins wrote:
Rowan,
What is confusing me is that i think you're seeing it as a major
implementation defect. To avoid arguable implementations, i've made
short example in Java:
System.out.println(new StringBuffer("noël").reverse().toString());
It does produce string
I'm not sure I understand what you're trying to do, could you explain in
more detail with examples?
PUT /url
Content-type: application/x-www-form-urlencoded
parse_str (file_get_contents(‘php://input'), $_POST) // Ok
PUT /url
Content-type: multipart/mixed; boundary=""
file_get_contents(‘ph
On 15 October 2014 22:14:32 GMT+01:00, Ralph Schindler
wrote:
>>> I'm not sure I understand what you're trying to do, could you
>explain in
>>> more detail with examples?
>>
>> PUT /url
>> Content-type: application/x-www-form-urlencoded
>>
>> parse_str (file_get_contents(‘php://input'), $_POST) /
Ok, i did a little test script, you can check, the browser sends to
the server a request body, but
var_dump(file_get_contents('php://input')) // string(0) ""
Do not forget to select a file to upload.
POST
2014-10-16 0:14 GMT+03:00 Ralph Schindler :
>>> I'm not sure I understand what you'
Hi!
> if($_SERVER['REQUEST_METHOD'] == 'POST')
> {
> var_dump(file_get_contents('php://input'));
> exit;
> }
I tried this script, if you do POST, your data is in $_FILES, if you do
PUT, your data is in php://input. Still not sure what is the big problem.
--
Stanislav Malyshev, Software Archit
2014-10-16 2:13 GMT+03:00 Stas Malyshev :
>
> I tried this script, if you do POST, your data is in $_FILES, if you do
> PUT, your data is in php://input. Still not sure what is the big problem.
I added the variable field, how do I get its value, with use the query
method PUT and enctype="multipar
Hi!
> I added the variable field, how do I get its value, with use the query
> method PUT and enctype="multipart/form-data"?
>
> This debate not for tediousness, this is a real problem, if you want
> to use the query method PUT and enctype="multipart/form-data",
> variable $_POST is empty and fil
2014-10-16 2:36 GMT+03:00 Stas Malyshev :
> No, file_get_contents('php://input') is not empty - I just checked it
> and if you send PUT request the whole request - files and all - is in
> the php://input. If you don't see it you might be doing something wrong.
Yes, you're right, I'm wrong tests,
hi Zeev,
On Tue, Oct 14, 2014 at 10:08 AM, Zeev Suraski wrote:
> All,
>
>
>
> We’ve had some discussions about it during the version name & phpng RFC
> processes, and now that 5.6.0 is behind us – I think it’s time to get a
> more concrete game plan for PHP 7.0.
>
>
>
> I drafted an RFC that prop
Dear Internals,
I finally have a working implementation for return types RFC[1] built
on top of master. There are a few notes in the PR[2] about the
implementation. I invite you all to review the PR and provide
feedback.
This means that I will soon move the return types RFC to voting phase.
If yo
19 matches
Mail list logo
