On 19/08/14 09:49, Michael Wallner wrote:
Hi PHP internals!
I've created an RFC for discussion:
Whether it is feasible to add pecl_http v2 to the core.
https://wiki.php.net/rfc/pecl_http
Just a heads up. People seem very confused because they read the docs on
php.net and don't
On 20/08/14 11:12, Marc Bennewitz wrote:
On 18.08.2014 17:43, Johannes Schlüter wrote:
On Mon, 2014-08-18 at 17:30 +0200, Johannes Schlüter wrote:
foreach ($db-query(SELECT id, title FROM entries) as $row) {
echo trtd;
if ($row[0] == $_GET['highlight_id']) {
On 19/08/14 01:59, Stas Malyshev wrote:
- EFFECTIVE IMMEDIATELY, we do not accept new non-security bugfixes into
5.4 branch unless they are very important ones (and that is only because
people may, in theory, have pending patches and we didn't give advance
notice). Importance would have to be
On 22/08/14 13:56, Julien Pauli wrote:
On Wed, Aug 20, 2014 at 10:45 PM, Stas Malyshev smalys...@sugarcrm.com
wrote:
Hi!
Apparently the fix for #67724 [2] caused #67865 [1], but I already have
a fix for the fix (oh my) [3].
I've reverted it from 5.4.32, but please commit this fix in 5.4.
On 2 Sep 2014 00:19, Chris Wright c...@daverandom.com wrote:
Good evening all
I've put together a patch for bug 67855 which can be seen here:
https://github.com/php/php-src/pull/778
The patch has so far received no feedback - does anyone have any?
If no-one has any objections to this, I
On 2 Sep 2014 00:13, Chris Wright c...@daverandom.com wrote:
Good evening all
I've put together a patch for bug 55600 which can be seen here:
https://github.com/php/php-src/pull/779
The patch has been updated based on various feedback and afaict is now
ready to be merged. Does anyone have
On 3 Sep 2014 11:47, Chris Wright c...@daverandom.com wrote:
On 2 September 2014 07:55, Lior Kaplan lio...@zend.com wrote:
On Sep 2, 2014 8:55 AM, Michael Wallner m...@php.net wrote:
On 2 Sep 2014 00:13, Chris Wright c...@daverandom.com wrote:
If no-one has any objections
On 07/09/14 14:25, Andrea Faulds wrote:
On 7 Sep 2014, at 13:22, Sherif Ramadan theanomaly...@gmail.com
wrote:
I've played around with this branch for a bit and seems reasonable,
passes the tests, and doesn't seem to have any serious
issues/memories leaks AFAICT.
There’s actually a
On 09/07/14 22:00, Stas Malyshev wrote:
Hi!
Having thought a bit about the subject, the heuristic I came up with was to
1) do not run tests from the same extension in parallel, and 2) do not run
tests from certain extensions in parallel (e.g., mysql and pdo_mysql).
How about making it a
On 10/09/14 19:41, Rowan Collins wrote:
Andrea Faulds wrote (on 09/09/2014):
If people want strict casting, we can add new functions or operators
for that specifically.
I think this came up during the previous discussion, and I actually
think it would be quite nice to have some functions
On 15 Sep 2014 05:59, Matt Ficken themattfic...@gmail.com wrote:
In making/merging major changes (like concurrency) the most important
thing is to not break that compatibility and dependability:
Your patch will fail without the /proc filesystem(mac osx?). On Windows,
you can check the
On 20 Sep 2014 04:15, Kris Craig kris.cr...@gmail.com wrote:
From what I can tell, there are valid arguments to be made for both, so I
would love to see some discussion/debate here regarding which solution
should be implemented, as I'm currently undecided. Also please feel free
to point
WTF is going on here? Looks like the vote was closed nearly 24 hours
early on a weekend. While the latter is not nice, closing early is a
no-go. So what are we going to do? Reopen the vote for another day or
completely restart it?
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development
On 2014-09-21 02:21, Sara Golemon wrote:
On Sat, Sep 20, 2014 at 3:03 PM, Leigh lei...@gmail.com wrote:
On 20 September 2014 20:47, Sara Golemon p...@golemon.com wrote:
I like the general idea, but rather than explicitly focusing on
the 'or' keyword, how about just giving all loop constructs
On 2014-09-22 14:08, Andrea Faulds wrote:
On 22 Sep 2014, at 12:06, Derick Rethans der...@php.net wrote:
I would also like to point out that, just like a 8:8 vote is not a
50% majority, 16:8 is technically also not a two thirds
*majority*. The RFC, like with many other important things is
On 2014-09-23 06:00, Sanford Whiteman wrote:
What would happen is it'd throw an E_DEPRECATED for at least the remainder
of 5.x, then throw the usual E_WARNING for a missing argument starting in
7.x with no default.
Sounds OK to me now that I've noticed this:
On 2014-09-23 09:30, Kris Craig wrote:
On Tue, Sep 23, 2014 at 12:24 AM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
On 2014-09-23 06:00, Sanford Whiteman wrote:
What would happen is it'd throw an E_DEPRECATED for at least the
remainder
of 5.x, then throw
On 2014-09-23 10:11, Sanford Whiteman wrote:
if somehost.example.com has the MX, it should return true with
checkdnsrr('somehost.example.com'). If example has the MX set to
somehost.example.com or similar, it should return true as well. Or am
I missing your point?
You are missing it, as
On 2014-09-23 10:04, Nicolai Scheer wrote:
Hi all,
until 5 minutes ago I thought it would be perfectly legal to use an object
as an array key, given that its __toString() method is in place.
Seems as if I was wrong.
I know that array keys are not what is considered string context
On 2014-09-23 10:47, Michael Wallner wrote:
On 2014-09-23 10:11, Sanford Whiteman wrote:
if somehost.example.com has the MX, it should return true with
checkdnsrr('somehost.example.com'). If example has the MX set to
somehost.example.com or similar, it should return true as well. Or am
I
On 2014-09-23 11:15, Leigh wrote:
On 23 September 2014 09:51, Michael Wallner m...@php.net wrote:
Yes, it was removed intentionally (quite a long time ago), like using
resources as array keys, to avoid hard-to-trace bugs for the user. At
least that's the reasoning I can remember.
He
On 2014-09-23 11:45, Leigh wrote:
On 23 September 2014 10:35, Michael Wallner m...@php.net wrote:
On 2014-09-23 11:15, Leigh wrote:
He doesn't want to add the object as a key, he wants to invoke __toString().
Did I write that?
No, you didn't, sorry.
I just didn't see how an object
On 24/09/14 02:08, Stas Malyshev wrote:
Hi!
I do believe that the UString class would benefit from such a change.
Why would it be confusing to implement this?
For some objects, it may lead to rather strange results - i.e.,
Exception has __toString() but probably not very useful one for
On 24/09/14 08:30, Stas Malyshev wrote:
Hi!
Well, then let's remove this restriction from resources, too.
Not sure what use would it be for resources - resource IDs are not
controlled by user code and for all intents and purposes are opaque
numbers, which also do not have to be unique
On 14/10/14 15:20, Ben Ramsey wrote:
I suppose we could make a super global that returns that for us, but it’s
just as easy to
use the above. Additionally, you might not want to put the full body of the
request into
memory like that. You might rather read the stream only a few bytes at a
On 14/10/14 16:08, Mike Dugan wrote:
Did I just name a global variable? W00t!
I guess Chris meant pecl_http's http\Env\Request::$form property.
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 14/10/14 17:02, Johannes Schlüter wrote:
On Tue, 2014-10-14 at 14:53 +0100, Chris Wright wrote:
PECL HTTP v2 already has this, actually:
http://devel-m6w6.rhcloud.com/mdref/http/Env/Request#
Also, I think Mike got the naming right there as well, $form is the
accurate description of
On 21 October 2014 14:35, Christian Schneider cschn...@cschneid.com wrote:
Am 21.10.2014 um 09:06 schrieb Joe Watkins pthre...@pthreads.org:
https://wiki.php.net/rfc/ustring
This is the result of work done by a few of us, we won't be
opening any
vote in a fortnight. We have
On 26/10/14 22:21, Stas Malyshev wrote:
Hi!
The only way to do this in PHP now is write a userland function that parses
multipart form data, which is non-trivial. I had written one, but would
It is true that PUT data need to be parsed, however it is not true you
have to implement MIME
On 27/10/14 08:09, Stas Malyshev wrote:
Hi!
I don't like this, mainly because it blocks a future direct use and storage
of objects as keys in an array, i.e. what SplObjectStorage does.
It does not. It just allows the objects to control how they are seen
when they are used as keys in
On 27/10/14 04:08, Will Fitch wrote:
On Oct 26, 2014, at 9:43 PM, Stas Malyshev smalys...@gmail.com
wrote:
Hi!
I’m trying to wrap my head around a real-world use-case with
this. We have spl_object_hash, which effectively provides a
unique hash for
This hash has nothing to do with
On 28/10/14 16:58, Ben Ramsey wrote:
On Oct 26, 2014, at 4:30 PM, Will Fitch willfi...@php.net wrote:
100% agree. Perhaps focusing on getting pecl/http v2 added as ext
or core should be the real discussion:
https://wiki.php.net/rfc/pecl_http
https://wiki.php.net/rfc/pecl_http.
I
On 02 11 2014, at 01:33, Rowan Collins rowan.coll...@gmail.com wrote:
On 01/11/2014 22:24, Andrea Faulds wrote:
Perhaps it would be worth ditching any attempts to change setcookie() (just
keep it around for backwards-compatibility), and to instead add a new
function, function family, or
On 11/11/14 10:13, Matteo Beccati wrote:
On 11/11/2014 09:57, Kalle Sommer Nielsen wrote:
Hi Matteo
2014-11-11 9:30 GMT+01:00 Matteo Beccati p...@beccati.com:
Hi,
I wasn't aware of this particular issue, until a few minutes ago (got a
bug report from a user). Any reason why:
On 26/11/14 16:29, Scott Arciszewski wrote:
That's a rather extreme reaction to trying to patch string operations that
real-world frameworks use to handle crypto secrets, don't you think?
Hmm, no.
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
On 11/12/14 09:36, Ferenc Kovacs wrote:
CCing Mike as he was the author who originally added 3.0 to the exclude
list.
Yes, I'm on ArchLinux, which has very recent software versions, so I
just added it to the exclude, when I upgraded bison to 3.0 and then
downgraded bison again.
IIRC ZTS
On 19/08/14 09:49, Michael Wallner wrote:
Hi PHP internals!
I've created an RFC for discussion:
Whether it is feasible to add pecl_http v2 to the core.
https://wiki.php.net/rfc/pecl_http
Just a minor update: the two PECL depencies have been ported to ZE3.
--
Regards,
Mike
On 17/12/14 00:45, Andrea Faulds wrote:
Hi Pierre,
On 16 Dec 2014, at 23:42, Pierre Joye pierre@gmail.com
wrote:
On Dec 17, 2014 4:19 AM, Andrea Faulds a...@ajf.me wrote:
Hmm, actually, a 2to3-esque tool and a formal extension of 5.6's
support by a year sounds like a better
On 18/12/14 01:38, Pierre Joye wrote:
On Dec 17, 2014 5:26 PM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
Just a minor update: the two PECL depencies have been ported to ZE3.
Btw, I still wonder if their features could be provided as part of php
instead of having to add 3
There's already ZEND_RESULT_CODE, or did I miss anything?
On 25 Dec 2014 06:45, Xinchen Hui larue...@php.net wrote:
Hey:
On Thu, Dec 25, 2014 at 12:38 PM, Pierre Joye pierre@gmail.com
wrote:
On Thu, Dec 25, 2014 at 3:06 PM, Andrea Faulds a...@ajf.me wrote:
On 24 Dec 2014, at 23:53,
On 04/02/15 08:24, Stanislav Malyshev wrote:
Hi!
Our header() function supports multiline HTTP headers, which are allowed
by RFC 2616. However, newer RFC -
https://tools.ietf.org/html/rfc7230#section-3.2.4 - deprecates them and
says:
Historically, HTTP header field values could be
On 04/02/15 09:52, Stanislav Malyshev wrote:
Hi!
Don't we prevent that already?
http://lxr.php.net/xref/PHP_5_6/main/SAPI.c#749
I'm not sure what you meant by that, but the code you linked to allows
multi-line headers according to RFC 2616 - this is what comment in line
750 means. I
On 03 02 2015, at 10:33, Julien Pauli jpa...@php.net wrote:
$HTTP_RAW_POST_DATA could as well disappear (made deprecated as of 5.6).
This is already gone in master, which reminds me of the missing UPGRADING note.
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To
Hi Stas!
On 05/02/15 00:43, Stanislav Malyshev wrote:
Hi!
Points explicitely marked for discussion in the RFC itself:
* pecl/propro
Proxies for properties representing state in internal C structs
https://wiki.php.net/rfc/pecl_http#peclpropro
* pecl/raphf
(Persistent) handle
On 05/02/15 09:05, reeze wrote:
Thanks a lot!
On 5 February 2015 at 16:03, Dmitry Stogov dmi...@zend.com wrote:
merged into master with the proposed changes.
Thanks. Dmitry.
Awesome, thank you!
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
On 30/01/15 17:45, Lester Caine wrote:
On 30/01/15 14:22, Michael Wallner wrote:
- default etag hash algo for dynamic response bodies has changed to
sha1 from crc32 and cannot be changed through an INI setting
etags on dynamic content are, well, subject to change anyway,
so I
On 3 Feb 2015 08:10, Adam Harvey ahar...@php.net wrote:
On 3 February 2015 at 03:11, Anatol Belski anatol@belski.net wrote:
properly after the voting phase the
https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts moves to the
voting. Each item is voted separately. The voting ends on
Hi Stas!
On 05/02/15 21:46, Stanislav Malyshev wrote:
Hi!
Uhm, I'm not sure I understand :-? Weren't I supposed to measure exacly
that? Let me know, if you wanted something else to be compared.
I wanted to know why we need persistent resources. You brought comparing
persistent resources
Hi!
Do we want to discuss anything further before I put this to vote again?
https://wiki.php.net/rfc/pecl_http
Points explicitely marked for discussion in the RFC itself:
* pecl/propro
Proxies for properties representing state in internal C structs
On 04/02/15 14:06, Pavel Kouřil wrote:
Hello,
as I mentioned already in the other thread - there are currently no
coding standards related to namespace naming in
https://github.com/php/php-src/blob/master/CODING_STANDARDS and the
coding standards should probably be updated before voting,
Hi Stas!
On 05/02/15 09:30, Stanislav Malyshev wrote:
The sole code change would be removing the check for POST, i.e.
`!strcasecmp(SG(request_method),POST)` so that actually any request
method with a recognized content-type (i.e. application/form-data or
application/x-www-form-urlencoded)
Hi Stas!
On 05/02/15 09:30, Stanislav Malyshev wrote:
Hi!
think raphf is far more of practical use. Why should HTTP, or even more
HTTPS or HTTP2, be any different than another service, especially when
Which another service?
Databases (see my pecl/pq example in the RFC), key/value stores,
On 05/02/15 09:53, Stanislav Malyshev wrote:
Hi!
Databases (see my pecl/pq example in the RFC), key/value stores, message
queues, whatever you can think of.
HTTP and databases are principally different. HTTP protocol is stateless
message-oriented protocol, and database connection
On 05/02/15 13:10, Julien Pauli wrote:
On Thu, Feb 5, 2015 at 2:08 AM, Andrea Faulds a...@ajf.me wrote:
Hi Hannes,
On 4 Feb 2015, at 23:58, Hannes Magnusson hannes.magnus...@gmail.com
wrote:
So what it supports more inputs?
It does constitute an LSP violation. more inputs is not what the
On 05/02/15 02:53, Yasuo Ohgaki wrote:
Hi all,
I would like to discuss my must have it in PHP 7 item.
PHP RFC: script() and script_once()
https://wiki.php.net/rfc/script_and_script_once
Forget about the INI setting.
I think the perfect fit for that feature would be import{,_once}, but
On 06/02/15 15:17, François Laupretre wrote:
You probably didn't live the PHP 4/5 migration
Now, this seems to become a habit.
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 14/01/15 18:53, Julien Pauli wrote:
Hello,
Had a discussion with Rasmus today.
It would be cool if we could have a PHP7 compat of our top-10 Pecl
extensions before our first PHP7 RC.
This will allow more people to help testing both PHP7 (some people may need
some of the top-10
On 15/01/15 17:31, Joshua Rogers wrote:
---
ext/phar/zip.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/ext/phar/zip.c b/ext/phar/zip.c
index 2a95580..2117b0e 100644
--- a/ext/phar/zip.c
+++ b/ext/phar/zip.c
@@ -1217,7 +1217,9 @@ int
On 15/01/15 15:51, Andrea Faulds wrote:
Let’s have a look. From a quick skim over the thread for v0.1:
* In favour of weak types (or the RFC anyway): Adam, Stas, yourself, Jordi,
Pierre,
Count me in for v0.1.
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To
On 14/01/15 23:13, Christian Stocker wrote:
Hi
On 14.01.15 22:21, Michael Wallner wrote:
On 14/01/15 18:53, Julien Pauli wrote:
After a quick glance at the PECL package stats (of packages wchich are
not already in kind of an exclusive/external maintainance status, and
which I used to use
On 19 Jan 2015 12:30, Ferenc Kovacs tyr...@gmail.com wrote:
On Mon, Jan 19, 2015 at 6:41 AM, Stanislav Malyshev smalys...@gmail.com
wrote:
Hi!
This is pretty horrible and should be fixed by making sure that
I don't see why it's so horrible. In fact, handling null is easier than
Hi!
Now, that I'm mostly done with porting pecl/http [1] and dependencies
(propro [2] and raphf [3]) to ZE3 I'd like to restart discussion on the
topic, whether it is feasible to add pecl_http as a bundled extension to
the core.
https://wiki.php.net/rfc/pecl_http
[1]
Why not leave it as it is? I mean, really, those five strokes?
Wherever it's going, I'm -1 on changing the meaning of the existing macro.
On 11 Feb 2015 16:01, reeze re...@php.net wrote:
Hi,
On 11 February 2015 at 19:15, Dmitry Stogov dmi...@zend.com wrote:
Hi,
I don't think it'll
On 06/02/15 17:44, Daniel Lowrey wrote:
If you doubt that this is a solved problem in userland consider the
performance of my own 100% userland HTTP client demonstrated here
without the use of curl or any other extensions:
https://gist.github.com/rdlowrey/54171625334670ccb9f5
I can
On 06/02/15 17:44, Daniel Lowrey wrote:
I’ve rewritten the RFC for pecl_http and hopefully addressed most of the
things mentioned previously.
I you still find anything lacking, please let me know, so I can
expand the
RFC accordingly.
And of course, everything else is up for discussion.
On 04/02/15 18:57, Pavel Kouřil wrote:
On Wed, Feb 4, 2015 at 6:17 PM, Andrea Faulds a...@ajf.me wrote:
Hey,
On 4 Feb 2015, at 17:10, Crypto Compress
cryptocompr...@googlemail.com wrote:
I would go with Http\
Why not the reserved Php\Http\?
This sounds good to me. php\ is already
On 17/02/15 23:03, Sara Golemon wrote:
1) Introduce scalar types for primitives: bool, int, float, string,
resource, object (we already have array)
1a) Introduce meta-types as pre-defined unions (we can add custom
unions in a later rfc). A possible list may be as follows (again, we
can
On 18/02/15 12:31, Rowan Collins wrote:
Michael Wallner wrote on 18/02/2015 11:19:
On 17/02/15 23:03, Sara Golemon wrote:
1) Introduce scalar types for primitives: bool, int, float, string,
resource, object (we already have array)
1a) Introduce meta-types as pre-defined unions (we can add
On 12/02/15 19:55, Thomas Punt wrote:
I'd like to propose to make empty() a variadic, where if any
arguments passed in are considered empty, then false is returned
Should that read if any arguments passed in are considered *NOT* empty,
then false is returned?
--
Regards,
Mike
--
PHP
On 19/02/15 03:44, Rasmus Lerdorf wrote:
but _999_ would need to work as well and _ is a valid char in a constant
so you can have a constant named _999_.
Why would we need to support the underscore in front (and maybe even at
the end) of a number?
--
Regards,
Mike
--
PHP Internals - PHP
On 19/02/15 13:16, Nikita Nefedov wrote:
Why not space? It's certainly possible (I just checked) and it would look
clear I guess:
my_func(1 999 999);
Yes, but what if I just missed one or two commas there? ;)
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing
Hi,
I drafted an RFC to continue output buffering despite an aborted
connection was detected. The title might well be a bit misleading, so
please read the RFC before judgement.
https://wiki.php.net/rfc/continue_ob
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To
Hi!
Please, consider this a warning that I'll put this to vote again shortly.
https://wiki.php.net/rfc/pecl_http
--
Regards,
Mike
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 23/01/15 09:27, Michael Wallner wrote:
On 23 01 2015, at 02:40, Pierre Joye pierre@gmail.com wrote:
On Thu, Jan 22, 2015 at 5:32 PM, Michael Wallner m...@php.net
wrote:
Hi!
Now, that I'm mostly done with porting pecl/http [1] and
dependencies (propro [2] and raphf [3]) to ZE3
On 22/01/15 19:51, Levi Morrison wrote:
Now, that I'm mostly done with porting pecl/http [1] and dependencies
(propro [2] and raphf [3]) to ZE3 I'd like to restart discussion on the
topic, whether it is feasible to add pecl_http as a bundled extension to
the core.
Hi,
Discussion has been very low on this topic since it was proposed on
August 19th, so I just opened the vote on the RFC whether to add
pecl_http to the core. The vote will be open until about 12:00 UTC on
Friday, February 6th.
https://wiki.php.net/rfc/pecl_http#vote
--
Regards,
Mike
--
Hi,
The vote has been cancelled on 2015-01-28 at 23:30 UTC due to concerns
about completeness of the RFC.
I'll rewrite it and put it back under discussion when ready.
Thank you all for your feedback.
Cheers,
Mike
On 28/01/15 21:32, Stanislav Malyshev wrote:
Hi!
Some feedback: I feel the RFC is not clear about the advantages and
disadvantages of including this package. Mostly, the RFC is hey I have
this package can we include it in core? I feel like it's fairly incomplete
Agreed. There needs to be
Hi!
I’ve rewritten the RFC for pecl_http and hopefully addressed most of the things
mentioned previously.
I you still find anything lacking, please let me know, so I can expand the RFC
accordingly.
And of course, everything else is up for discussion.
Thanks,
Mike
--
PHP Internals - PHP
On 29/01/15 12:32, Yasuo Ohgaki wrote:
Hi Mike,
Awesome work!
On Thu, Jan 29, 2015 at 8:14 PM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
I’ve rewritten the RFC for pecl_http and hopefully addressed most of
the things mentioned previously.
I you still find
On 30/01/15 20:19, Stanislav Malyshev wrote:
Hi!
Just because that most of the code YOU have seen uses CamelCase does not
mean that CamelCase is the standard. I programmed in other languages for
over 20 years before I switched to PHP, and in those languages the standard
was snake_case. That
Hi Stas!
On 30/01/15 20:10, Stanislav Malyshev wrote:
Hi!
I’ve rewritten the RFC for pecl_http and hopefully addressed most of the
things mentioned previously.
Thank you, Michael, this is much better!
I would still like to hear more about 2 extensions, especially about
raphf - it
On 31 Jan 2015 06:04, Rasmus Lerdorf ras...@lerdorf.com wrote:
There is something weird going on with PHP7 and the moodle_page class
and all its magic methods. It dies with a:
/var/www/moodle/blocks/navigation/block_navigation.php(223) : Notice -
Undefined property: moodle_page::$navigation
On 23/01/15 22:18, Jan Ehrhardt wrote:
Dmitry Stogov in php.internals (Fri, 23 Jan 2015 17:54:45 +0400):
master branch.
propro, raphf and pecl_http do not compile with the master branch.
You'll have to checkout the phpng branch. These extensions did compile
and load:
On 23 01 2015, at 02:40, Pierre Joye pierre@gmail.com wrote:
On Thu, Jan 22, 2015 at 5:32 PM, Michael Wallner m...@php.net wrote:
Hi!
Now, that I'm mostly done with porting pecl/http [1] and dependencies
(propro [2] and raphf [3]) to ZE3 I'd like to restart discussion on the
topic
On 22 01 2015, at 19:51, Levi Morrison le...@php.net wrote:
Now, that I'm mostly done with porting pecl/http [1] and dependencies
(propro [2] and raphf [3]) to ZE3 I'd like to restart discussion on the
topic, whether it is feasible to add pecl_http as a bundled extension to
the core.
On 23 01 2015, at 04:42, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Could you include http_build_query() modification in the RFC?
http_build_query() escapes ' ' as '+' currently. It should be '%20'.
I was about to proposing this change, but it was http_* function and
the change does not
On 23 01 2015, at 09:11, Michael Wallner m...@php.net wrote:
On 23 01 2015, at 04:42, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Could you include http_build_query() modification in the RFC?
http_build_query() escapes ' ' as '+' currently. It should be '%20'.
I was about to proposing
On 02 02 2015, at 07:51, François Laupretre franc...@tekwire.net wrote:
Sorry to say that, but are you sure you understand the difference between
zval types and resource types ?
Thanks, you made my day.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
On 02 02 2015, at 09:01, Sara Golemon p...@golemon.com wrote:
On 2 Feb 2015, at 06:43, Xinchen Hui larue...@php.net wrote:
furthermore, I'd like to discuss remove the handle in zend_resource struct..
it may breaks some usage (use resource as long/double/string
I've seen uses in the
On 02 02 2015, at 00:49, Andrea Faulds a...@ajf.me wrote:
Good evening,
The RFC has been updated to cover return types, since Levi’s Return Types RFC
has passed. The patch is a work in progress: it works, but lacks tests for
return types.
Version 0.3 of the RFC can be found here:
On 28/01/15 18:58, Levi Morrison wrote:
On Wed, Jan 28, 2015 at 10:53 AM, Levi Morrison le...@php.net
mailto:le...@php.net wrote:
Discussion has been very low on this topic since it was proposed on
August 19th, so I just opened the vote on the RFC whether to add
On 28/01/15 19:08, Nikita Popov wrote:
On Wed, Jan 28, 2015 at 1:17 PM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
Hi,
Discussion has been very low on this topic since it was proposed on
August 19th, so I just opened the vote on the RFC whether to add
On 28/01/15 19:03, Andrea Faulds wrote:
Hi Levi,
On 28 Jan 2015, at 17:58, Levi Morrison le...@php.net wrote:
Oh, one more item: has anyone had time to review the pieces and how
they all interact, as well as reviewing the quality of each
component? I should hardly think in the time given
On 28/01/15 20:07, Matteo Beccati wrote:
On 28/01/2015 13:17, Michael Wallner wrote:
Discussion has been very low on this topic since it was proposed on
August 19th, so I just opened the vote on the RFC whether to add
pecl_http to the core. The vote will be open until about 12:00 UTC
On 28/01/15 20:18, Andrea Faulds wrote:
Hi Michael,
On 28 Jan 2015, at 19:13, Michael Wallner m...@php.net wrote:
- Client
The http stream wrapper is a hack and the existing libcurl binding
is subpar. They could be improved separately, but that is not
subject of this RFC.
Currently
I'll forward this to internals, Chris.
On 28/01/15 18:43, christopher jones wrote:
On 1/28/15 9:28 AM, Michael Wallner wrote:
On 28/01/15 18:22, christopher jones wrote:
On 1/28/15 9:17 AM, Michael Wallner wrote:
On 28/01/15 18:01, christopher jones wrote:
On 1/28/15 4:17 AM, Michael
On 28/01/15 21:03, Levi Morrison wrote:
On Wed, Jan 28, 2015 at 11:12 AM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
On 28/01/15 18:58, Levi Morrison wrote:
On Wed, Jan 28, 2015 at 10:53 AM, Levi Morrison le...@php.net
mailto:le...@php.net
mailto:le...@php.net
On 30/01/15 15:08, Ferenc Kovacs wrote:
On Fri, Jan 30, 2015 at 2:45 PM, Michael Wallner m...@php.net
mailto:m...@php.net wrote:
https://wiki.php.net/rfc/pecl_http
hi,
just a small question: what will be the upgrade path for existing
pecl_http users upgrading to 7.0?
I'd
On 08/02/15 23:25, Stanislav Malyshev wrote:
Youself said that HTTP is a stateless protocol, so how would a
connection in an unclean state look like in your opinion?
Connection and protocol are different things. In connection, you could
be in the middle of the protocol - i.e. sending
401 - 500 of 605 matches
Mail list logo
