[PHP-DEV] PHP 8.2.20RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.20 should be expected in 2 weeks, i.e. on June 6th, 2024. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/bbfefee22776e04505286d9ba6d27c0d Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron & Ben Ra

[PHP-DEV] PHP 8.2.18 Released!

-8.2> Changelog:<https://php.net/ChangeLog-8.php#8.2.18> Release Manifest: <https://gist.github.com/adoy/3d3a965ce597435758024dce156a8447> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Rams

[PHP-DEV] PHP 8.2.16 Released!

.16> Release Manifest: < https://gist.github.com/adoy/63bd01f657b3f5cd6e5a271494349c68> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.16.tar.bz2 SHA256 hash: 2658c1b8935ab6b53a7f209354602761ab07066e66920bc472b8815fd1b4

[PHP-DEV] PHP 8.2.16RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.16 should be expected in 2 weeks, i.e. on February 15th, 2024. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/a93b3f88ae9a677d7ef8c5466d312e14 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron &

[PHP-DEV] PHP 8.2.14 Released!

.14> Release Manifest: <https://gist.github.com/adoy/643bcae413fd13f57990cbaf9b615d09> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.14.tar.bz2 SHA256 hash: f871e131333d60ae6c537b1adddbc2aea54c436c562af986fb8309c06004

[PHP-DEV] PHP 8.2.14RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.14 should be expected in 2 weeks, i.e. on December 21th, 2023. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/b0daf2b42dd7aff34f2b611619dc3adf Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron &

[PHP-DEV] PHP 8.2.12 Released!

.12> Release Manifest: <https://gist.github.com/adoy/6af8976401618c3147c171f5be4bfc89> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.12.tar.bz2 SHA256 hash: 704325f56b1b4c17f9f951e1ffef5c64e148896053f34e2626152cbaa2f0

[PHP-DEV] PHP 8.2.12RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.12 should be expected in 2 weeks, i.e. on October 26th, 2023. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/e7730e3cfe0c98ac6c2f471149f80eef Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron &

[PHP-DEV] PHP 8.2.10 Released!

.10> Release Manifest: <https://gist.github.com/adoy/a2c338db8cc96297f20bfb2c89a98587> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.10.tar.bz2 SHA256 hash: cc9834e8f1b613d7677af8843c3651e9829abca8ebfe9079251d0d85d9a0

[PHP-DEV] PHP 8.2.10RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.10 should be expected in 2 weeks, i.e. on August 31th, 2023. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/78c38faa107a4fe3c2901d65d7afb176 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron &

[PHP-DEV] PHP 8.2.7 Released!

2.7> Release Manifest: <https://gist.github.com/adoy/0928b86b24ec5a1bae905364b88f11f8> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.7.tar.bz2 SHA256 hash: 5bfb2a35c67921bdcadd5c90cb290ad7537d24da113a5e8bc2d646b02de7

[PHP-DEV] PHP 8.2.7RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.7 should be expected in 2 weeks, i.e. on June 8th, 2023. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/0f99a1daafa21db2d4b2179e56519e29 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron & Ben Ra

Re: [PHP-DEV] [VOTE] PHP 8.3 Release Managers

Congratulations ! Eric, Jakub I'll be in touch with you soon. Pierrick Le ven. 31 mars 2023, à 18 h 54, Sergey Panteleev a écrit : > Hi all, > > In the role of "Veteran" release manager, Pierrick Charron [0], the PHP > 8.2 release manager, > has volunteered

[PHP-DEV] PHP 8.2.5 Released!

2.5> Release Manifest: < https://gist.github.com/adoy/ff01bd80fa225d35757b8077fe9af2c3> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.5.tar.bz2 SHA256 hash: e5a80663cca4f6044ad86a489798147c7af037eca96f6cd357ab36d28cb6

[PHP-DEV] PHP 8.2.5RC1 available for testing

://github.com/php/php-src/issues PHP 8.2.5 should be expected in 2 weeks, i.e. on April 13th, 2023. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/605566c637bf18d7e817e1061a0c0602 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron & Ben Ra

Re: [PHP-DEV] Release Managers for PHP 8.3

be considered a > candidate. An initial TODO page has been added to the wiki and contains > provisional dates for GA and pre-releases [2]. > > [1] https://github.com/php/php-src/blob/master/docs/release-process.md > [2] https://wiki.php.net/todo/php83 > > Let's all make PHP awesome! > Pierrick Charron, Sergey Panteleev & Ben Ramsey >

[PHP-DEV] PHP 8.2.3 Released!

-8.2> Changelog:<https://php.net/ChangeLog-8.php#8.2.3> Release Manifest: <https://gist.github.com/adoy/84a1d24d540ab7bf637370bcb1c56063> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ram

[PHP-DEV] PHP 8.2.1 Released!

2.1> Release Manifest: <https://gist.github.com/adoy/c6aaeec96698f6005419df666eef054f> Many thanks to all the contributors and supporters! Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.1.tar.bz2 SHA256 hash: 75d6f8f365993ec0d1d9c6281d4557e6feec5a26194a468b8b01459d177e

[PHP-DEV] PHP 8.2.1RC1 available for testing

, Pierrick Charron & Ben Ramsey php-8.2.1RC1.tar.bz2 SHA256 hash: 2bd8d594fdaad246c9269d6e215850886f7abc44b00b8a20f28524ba61cf3b71 PGP signature: -BEGIN PGP SIGNATURE- iQJFBAABCgAvFiEEEZjAEXWTSXpexcGZKGrx+Yl0adwFAmOZGg0RHHBpZXJyaWNr QHBocC5uZXQACgkQKGrx+Yl0adw22Q//QsjxUSMeCfENhbpQJcD8MhfAoS4e

[PHP-DEV] PHP 8.2.0RC7 available for testing

, Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.0RC7.tar.bz2 SHA256 hash: dedd83919b6483399ef5896ff2f08f1f0e8e599ab4ff6d4c4ad1c6c711c8fdbd PGP signature: -BEGIN PGP SIGNATURE- iQJFBAABCgAvFiEEEZjAEXWTSXpexcGZKGrx+Yl0adwFAmN9ED8RHHBpZXJyaWNr QHBocC5uZXQACgkQKGrx+Yl0ad

[PHP-DEV] PHP 8.2.0RC5 available for testing

, Pierrick Charron & Ben Ramsey php-8.2.0RC5.tar.bz2 SHA256 hash: 0c20a018520531f8fc2fef47131a280e26c2c0575b1b724b5d6afc61ebb7695c PGP signature: -BEGIN PGP SIGNATURE- iQJFBAABCgAvFiEEEZjAEXWTSXpexcGZKGrx+Yl0adwFAmNYIeERHHBpZXJyaWNr QHBocC5uZXQACgkQ

[PHP-DEV] PHP 8.2.0RC3 available for testing

, Pierrick Charron & Ben Ramsey php-8.2.0RC3.tar.bz2 SHA256 hash: 3563c27710ce82136a5326ef915b1a006c2d3c7d7a02b424221ed38a01a76199 PGP signature: -BEGIN PGP SIGNATURE- iQJFBAABCgAvFiEEEZjAEXWTSXpexcGZKGrx+Yl0adwFAmMzcNQRHHBpZXJyaWNr QHBocC5uZXQACgkQKGrx+Yl0adzTGhAA

[PHP-DEV] PHP 8.2.0RC1 available for testing

, Pierrick Charron & Ben Ramsey php-8.2.0RC1.tar.bz2 SHA256 hash: baa8cf5ecfc97940ddb9a09734d1eb69242e7056351517ab246a78f0ed0b0bdf PGP signature: -BEGIN PGP SIGNATURE- iQJFBAABCgAvFiEEEZjAEXWTSXpexcGZKGrx+Yl0adwFAmMONR8RHHBpZXJyaWNr QHBocC5uZXQACgkQ

[PHP-DEV] PHP 8.2 branch out

Hi internals, We've just branched out the `PHP-8.2` branch : https://github.com/php/php-src/tree/PHP-8.2 With that, `master` is now open for PHP 8.3 development : Please remember to include the `PHP-8.2` branch in all merges from `PHP-8.1` and earlier and commit all the changes from the

[PHP-DEV] PHP 8.2.0 Beta 3 available for testing

://github.com/php/php-src/issues 8.2.0RC1 should be expected in 2 weeks, i.e. on Sept 1st 2022. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/37f80d10531f0250f4111a7b3034e357 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron & Ben Ra

[PHP-DEV] Strict properties and unserialization

Hi internals, We (Sergey and I) would like to introduce you to a problem [1] that was reported by Tim Düsterhus and others about the Strict Properties RFC [2] that was implemented in PHP8.2. The RFC missed a part about how PHP should handle unserialization of objects with undefined properties.

[PHP-DEV] PHP 8.2.0 Beta 1 available for testing

://gist.github.com/adoy/81f41a2b833275bd2d00b7165907540e Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron & Ben Ramsey php-8.2.0beta1.tar.bz2 SHA256 hash: ab7292701c12393892cfc7c2d93f8d2701946d073c87a1e05619da3e04a009a7 PGP signature: -BEGIN PGP SIGNA

[PHP-DEV] Re: [RFC][Vote] New Curl URL API

Hi Internals, The RFC has been declined with a vote of 10 in favor and 14 against. Thank you for the votes. Le lun. 4 juill. 2022, à 19 h 34, Pierrick Charron a écrit : > Hi internals, > > I opened voting for the new Curl URL API as part of PHP8.2. > > All recent discussio

Re: [PHP-DEV] [PHP8.2] Feature freeze in 2 weeks

ck Le mar. 12 juill. 2022, à 11 h 09, Rowan Tommins a écrit : > On 05/07/2022 19:08, Pierrick Charron wrote: > > This is yet another friendly reminder from your RMs that the PHP 8.2 > feature > > -freeze is in 2 weeks now [1]. All RFC targeting 8.2 should now be in the > > v

[PHP-DEV] [PHP8.2] Feature freeze in 2 weeks

Hi internal, This is yet another friendly reminder from your RMs that the PHP 8.2 feature -freeze is in 2 weeks now [1]. All RFC targeting 8.2 should now be in the voting phase to respect the minimal period of 2 weeks. Also it would be appreciated if some of internal devs could start reviewing

Re: [PHP-DEV] [RFC][Vote] New Curl URL API

Sorry about that const CURLUPART_USER = UNKNOWN; // what UNKNOWN? > UNKNOWN means that the value here is not relevant for the user to know. But for clarification, the values of those constants will be the exact same values of the same constants in libcurl. "All errors of libcurl will become

[PHP-DEV] Re: [RFC][Vote] New Curl URL API

Sorry, I forgot to include the RFC Url : https://wiki.php.net/rfc/curl-url-api Le lun. 4 juill. 2022, à 19 h 34, Pierrick Charron a écrit : > Hi internals, > > I opened voting for the new Curl URL API as part of PHP8.2. > > All recent discussions show that we are not even c

[PHP-DEV] [RFC][Vote] New Curl URL API

Hi internals, I opened voting for the new Curl URL API as part of PHP8.2. All recent discussions show that we are not even close to getting a consensus on how the new CurlUrl OO API should be done. After changing my mind 300 times in the last day, I decided to only propose the procedural

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hi all, > - The new CurlUrl class should probably be immutable from the start. It > was my biggest mistake not to do that with DateTime. > > After thinking about it and some discussions, I followed Derick's recommendation and therefore changed the RFC to make the CurlUrl class immutable. All the

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hi Rowan > If I've got a URL, which is already a string, what code would I write to > "do some checks" on it, outside of a unit test? > That's just an example with an old version of PHP, but let's say you have some code that makes requests but only to a specific list of servers, so you want to

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hi Rowan > > Rather than a *representation* of a URL, think of the class as a > *builder* for URLs. There are multiple methods because you might want to > build the URL in different orders ("start with this URL but replace the > port", "start with this domain and I'll add the path later", etc).

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

rzuchalski < michal.brzuchal...@gmail.com> a écrit : > Hi Pierrick > > śr., 22 cze 2022 o 06:38 Pierrick Charron napisał(a): > >> Hi, >> >> Following our discussions we had on the subject of the new Curl URL API, >> and other curl improvements. I decided to onl

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

ey don't care if they prefer one approach or the other and of course why ? I was thinking about doing a vote on this, but I'm not sure it's a good idea. What do you all think ? Regards, Pierrick Le jeu. 23 juin 2022, à 12 h 49, Levi Morrison a écrit : > On Tue, Jun 21, 2022 at 10

[PHP-DEV] PHP 8.2.0alpha2 is available for testing

://github.com/php/php-src/issues 8.2.0alpha3 should be expected in 2 weeks, i.e. on July 7th 2022. Hash values and PGP signatures can be found below or at https://gist.github.com/adoy/33f3c8fff8ccaa80d57079cb849cc9c3 Thank you, and happy testing! Regards, Sergey Panteleev, Pierrick Charron &

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

HI Hans, any particular reason CurlUrl::getPort() defaults to 0 rather than one of > the valid options? (that being CurlUrl::DEFAULT_PORT > and CurlUrl::NO_DEFAULT_PORT ) > This is because the default is none of those 2 behaviours, If the port wasn't set it will return null, but if the port is

Re: [PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hi Derick, > > - The new CurlUrl class should probably be immutable from the start. It > was my biggest mistake not to do that with DateTime. > > Thanks for sharing your lessons learned. But I still see some use cases where mutable objects are easier to use. From the experience you had with

[PHP-DEV] [RFC] [Under Discussion] New Curl URL API

Hi, Following our discussions we had on the subject of the new Curl URL API, and other curl improvements. I decided to only focus on adding the new Curl URL API and put aside all other improvements. Here is the RFC that reflects our current conversations. https://wiki.php.net/rfc/curl-url-api

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

> > > I haven't read back through the thread, but my impression was that *for > the curl URL facility specifically* the opposite was the case: a simple > object with no procedural equivalent would be everyone's preference. > CurlFile provides enough of a precedent for adding that IMO. > +1 > >

[PHP-DEV] [PHP 8.2] 30 days before feature freeze

Hi internal, This is a friendly reminder from your RMs that the PHP 8.2 feature-freeze is in a month now [1] and time flies. If you plan to submit a RFC you have until July 5th to open it for vote so that it can be closed on time. Regards, Sergey, Pierrick and Ben [1]

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

19 June 2022 03:53:17 BST, Pierrick Charron wrote: > > > >I hope you don't mind, I took some of your code from your "Enable > >strict_types checking for curl_setopt()" pull request [1] to do some test > >on introducing this but only on the OOP API. It's working ver

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

Hi Sara > This is so bizarre, I *know* I wrote an OOPified cURL extension some years > ago (called it curli), and now I can't find it anywhere. What universe am > I even in? > I don't know but if you pass through the parallel universe where Curli is, I'm interested. > > Anyway, +1 on making

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

Hi Rowan, all, Thanks for your responses and comments. > I think it's perfectly reasonable for CurlUrl to be designed the same way, > regardless of what else we do with the extension. > As suggested by most of you, I created a new version of the proposed new URL API with a friendlier interface

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

ven. 17 juin 2022, à 04 h 27, Lynn a écrit : > Good timezone! > > On Thu, Jun 16, 2022 at 11:44 PM Pierrick Charron > wrote: > >> About making a "Good OOP API", of course the goal is to make a *Good* OOP >> API. But there are things to take into consideration.

Re: [PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

ld do with the existing API ? Pierrick [1] https://github.com/php/php-src/blob/master/ext/curl/interface.c#L382 Le jeu. 16 juin 2022, à 15 h 48, Larry Garfield a écrit : > On Thu, Jun 16, 2022, at 2:10 AM, Pierrick Charron wrote: > > Hi internals, > > > > Since its version

[PHP-DEV] Discussion about new Curl URL API and ext/curl improvements

Hi internals, Since its version 6.62.0 [1], libcurl features a brand new URL API [2] that can be used to parse and generate URLs, using libcurl’s own parser. One of the goals of this API is to tighten a problematic vulnerable area for applications where the URL parser library would believe one

Re: [PHP-DEV] Re: [8.2] Release Manager Election

elease managers are: > > > > * Sergey Panteleev > > * Pierrick Charron > > > Congrats to Sergei and Pierrick! > > > Do you have a twitter account ? > > > Cheers, > Remi >

Re: [PHP-DEV] Re: [8.2] Release Manager Election

> > > > Refs: > > > 0 - Ben Ramsey: https://news-web.php.net/php.internals/117664 > > > 1 - Sergey Panteleev: https://news-web.php.net/php.internals/117596 > > > 2 - Evan Sims: https://news-web.php.net/php.internals/117621 > > > 3 - Aaron Junker:

Re: [PHP-DEV] PHP 8.2 Release Manager Selection

Hi, I would also like to present myself as a Rookie RM for PHP8.2 For those of you who don't know me, my name is Pierrick. I am French (that explains my grammar mistakes) and have been living in Montreal, Canada for 15 years now and have been working with PHP since then. I made my first

[PHP-DEV] Best way to fix #71929 curl_getinfo($ch, CURLINFO_CERTINFO)

Hi, I'm currently looking at bug #71929 and i'm wondering what is the best way to fix it. Basically the bug is that currently ext/curl tries to parse the "Subject" and "Issuer" returned by lib/curl to return this information as a PHP array. Here is the actual output : array ( 'Subject' =>

[PHP-DEV] [RFC][Accepted] Add curl_multi_errno(), curl_share_errno() and curl_share_strerror()

Hi, The vote on the RFC https://wiki.php.net/rfc/new-curl-error-functions#vote is now closed. The RFC was accepted with 23 "Yes" and 0 "No". I'll merge the patch in the master branch this week-end. Thanks to anybody who contributed to this RFC by voting. Pierrick

[PHP-DEV] [VOTE] Add curl_multi_errno(), curl_share_errno() and curl_share_strerror()

Hi Internals, Since I got no feedback on the RFC about the addition of those 3 functions and that this is not a big change I decided to open the vote. https://wiki.php.net/rfc/new-curl-error-functions Feedback and questions are as always welcome !

[PHP-DEV] [RFC][Accepted] Catching Multiple Exception Types

Hi, The vote on the RFC https://wiki.php.net/rfc/multiple-catch#vote is now closed. The RFC was accepted with 40 "Yes" and 6 "No". I'll merge the patch in the master branch today. Thanks to anybody who contributed to this RFC by voting or giving us feedback. Bronisław and Pierrick

[PHP-DEV] [RFC][Discussion] Add curl_multi_errno(), curl_share_errno() and curl_share_strerror()

Hi Internals, I would like to introduce 3 new functions to ext/curl - curl_multi_errno() - curl_share_errno() - curl_share_strerror() With those 3 functions added, it will now be possible to get any error that curl detect on any of the curl resource types and the error message associated to it.

Re: [PHP-DEV] Re: ext/curl update

> -Original Message- > > From: pierr...@webstart.fr [mailto:pierr...@webstart.fr] On Behalf Of > Pierrick > > Charron > > Sent: Wednesday, April 27, 2016 6:20 PM > > To: Anatol Belski <anatol@belski.net> > > Cc: Davey Shafik <da...@php.net>;

Re: [PHP-DEV] Re: ext/curl update

Sorry for the 2 mails but I forgot to give you the URL : https://github.com/php/php-src/pull/1890/files On 27 April 2016 at 19:14, Pierrick Charron <pierr...@adoy.net> wrote: > Hi Anatol, > > I created a new patch from the one first published but this time this one > target 7

Re: [PHP-DEV] Re: ext/curl update

> Hi, > > > -Original Message- > > From: pierr...@webstart.fr [mailto:pierr...@webstart.fr] On Behalf Of > Pierrick > > Charron > > Sent: Wednesday, April 27, 2016 2:20 PM > > To: Anatol Belski <anatol@belski.net> > > Cc: Davey Shafik <da...@p

Re: [PHP-DEV] Re: ext/curl update

net> wrote: > Hi, > > > -Original Message- > > From: m...@daveyshafik.com [mailto:m...@daveyshafik.com] On Behalf Of Davey > > Shafik > > Sent: Sunday, April 24, 2016 2:25 AM > > To: Pierrick Charron <pierr...@adoy.net> > > Cc: PHP internals

Re: [PHP-DEV] [RFC] PHP Attributes

On 27 April 2016 at 03:27, Dmitry Stogov <dmi...@zend.com> wrote: > > > On 04/27/2016 08:25 AM, Pierrick Charron wrote: > > Hi all, > > First of all thanks dmitry for your great work and for bringing the RFC > back to life. > > I think it would be grea

Re: [PHP-DEV] [RFC] PHP Attributes

Hi all, First of all thanks dmitry for your great work and for bringing the RFC back to life. I think it would be great to allow users to define their own annotations and give them some structure (what the annotation is made of). For example let's say I apply an annotation to define that a

Re: [PHP-DEV] [RFC] PHP Attributes

And it will probably be in conflict with the Short Array Syntax ? On 26 April 2016 at 13:14, Dmitry Stogov wrote: > Just because HHVM is closer to PHP than C#. > > > > From: Dominic Grostate > Sent: Tuesday, April

[PHP-DEV] Re: ext/curl update

rt. > > I hope to eventually (7.2+) use libnghttp2 to add an ext/nghttp2 HTTP > client and update the HTTP streams layer to support HTTP/2 also. > > I'd welcome your collaboration on any of this. > > - Davey > > On Sat, Apr 23, 2016 at 12:30 PM, Pierrick Charron <

[PHP-DEV] ext/curl update

Hi internals, I took some time to add some easy to implement new "features" that were implemented in libcurl but missing in ext/curl. Most of them are just exposing a new constant in ext/curl and dispatched in the curl_setopt function. I created a branch over master but the patch is applicable

Re: [PHP-DEV] [RFC] PHP Attributes

On 22 April 2016 at 11:39, guilhermebla...@gmail.com < guilhermebla...@gmail.com> wrote: > On Fri, Apr 22, 2016 at 3:07 AM, Dmitry Stogov wrote: > > > > > > > On 04/22/2016 04:05 AM, guilhermebla...@gmail.com wrote: > > > > Hi Dmitry, > > > > As a previous suggester of metadata

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

and I'll of course comply to the voters decision :-) Pierrick On 15 March 2016 at 12:23, Patrick ALLAERT <patrickalla...@php.net> wrote: > Hi, > > Le mer. 9 mars 2016 à 14:08, Marco Pivetta <ocram...@gmail.com> a écrit : > >> On 9 March 2016 at 14:03, Pierrick Cha

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

xception */ >> function packeForMe(string $name) : Pack >> { >> try { >> return (new Packer())->pack(new PackTemplate($name)); >> } catch (PackingFailed | ValidationException $e) { >> throw new SomeException($e); // or return null

Re: [PHP-DEV] [RFC Proposal] Null Coalesce Equal Operator

Hi Sara, Just to let you know that I took the liberty to correct the title of your RFC. It was still null coalesce equal operator :) Otherwise I'm +1 for both RFC Pierrick On 10 March 2016 at 22:01, Sara Golemon wrote: > On Wed, Mar 9, 2016 at 10:14 AM, Midori Kocak

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

On 9 March 2016 at 08:30, Marco Pivetta <ocram...@gmail.com> wrote: > On 9 March 2016 at 14:24, Pierrick Charron <pierr...@adoy.net> wrote: >> >> The thing I don't like about this approach is that I have to read the >> code and double check to make sure that

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

On 9 March 2016 at 08:08, Marco Pivetta <ocram...@gmail.com> wrote: > On 9 March 2016 at 14:03, Pierrick Charron <pierr...@adoy.net> wrote: > >> Hi Derick >> >> I agree that most of the time the best solution is to implement a clean >> ex

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

only possible when you control the exception hierarchy in your own code, but not possible when you don't control the code." On 9 March 2016 at 06:52, Derick Rethans <der...@php.net> wrote: > Hi! > > On Tue, 8 Mar 2016, Pierrick Charron wrote: > > > Bronisław Białek and

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

) } catch (AccessException $e) { return false; } catch (UnexpectedTypeException $e) { return false; } And other piece of code using multiple libraries. On 8 March 2016 at 18:06, Björn Larsson <bjorn.x.lars...@telia.com> wrote: > Den 2016-03-08 kl. 22:42, skrev Pierrick Charron: > >

Re: [PHP-DEV] [RFC Discussion] Catching multiple exception types

needed (Behaviour will stay the same, unless you see other behaviour that this syntax could have in this same "catch" context). Pierrick On 8 March 2016 at 16:50, Sean DuBois <s...@siobud.com> wrote: > On Tue, Mar 08, 2016 at 04:42:29PM -0500, Pierrick Charron wrot

[PHP-DEV] [RFC Discussion] Catching multiple exception types

Hi internals, Bronisław Białek and I would like to start a discussion about allowing multiple exception types to be caught in a single catch statement. https://wiki.php.net/rfc/multiple-catch A working implementation and tests are available in the RFC. We are waiting for your constructive

Re: [PHP-DEV] Re: [VOTE] Removal of curl-wrappers

David, All, I just committed the patch to remove curl-wrappers from PHP5.5. It 's one day before schedule but we need to make sure the merge was done before the new beta release. Pierrick On 22 April 2013 13:10, Pierrick Charron pierr...@adoy.net wrote: Hi, The vote is supposed to end

Re: [PHP-DEV] Re: [VOTE] Removal of curl-wrappers

Hi, The vote is supposed to end on April 24th, but if there is no objection, I will end it tomorrow and merge it if there is no change in the vote results. Pierrick On 22 April 2013 04:58, David Soria Parra d...@php.net wrote: On 2013-04-17, Pierrick Charron pierr...@adoy.net wrote

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

Hi, Since we are in a tight schedule, I started the vote and it will end in a week. https://wiki.php.net/rfc/curl-wrappers-removal-rfc#vote Pierrick On 16 April 2013 09:17, Julien Pauli jpa...@php.net wrote: On Tue, Apr 16, 2013 at 3:01 PM, Pierrick Charron pierr...@adoy.netwrote: I

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

Oh sorry I'm gonna do it right now. Thanks :) On 17 April 2013 18:02, Hannes Magnusson hannes.magnus...@gmail.com wrote: I think by law you have to create a new thread and prefix the subject line with [VOTE] or something. -Hannes On Wed, Apr 17, 2013 at 2:59 PM, Pierrick Charron pierr

[PHP-DEV] [VOTE] Removal of curl-wrappers

Hi folks, I just opened a vote for the curl-wrappers removal in 5.5. Since we are in a tight schedule, the vote duration will only be a week and will end April 24th. You can vote there : https://wiki.php.net/rfc/curl-wrappers-removal-rfc#vote Regards, Pierrick

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

I created a straightforward RFC that you can access here https://wiki.php.net/rfc/curl-wrappers-removal-rfc . If someone have something more to add in it, feel free. Otherwise I will start the vote so that we could remove it in 5.5 ASAP. Thanks Pierrick On 12 April 2013 11:09, Julien Pauli

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

at 11:17 PM, Pierrick Charron pierr...@adoy.net wrote: Including 5.3 and 5.4 ?? If removed in 5.3 and 5.4, theres no need for the constant anymore. Right :-) I agree with Pierre as well, we know this feature leads to bugs, is experimental, and is so not very very used. 5.3

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

If you decide to remove it for 5.5 RC, tell me and I'll merge this branch https://github.com/adoy/php-src/tree/remove-curl-wrappers Thanks Pierrick On 11 April 2013 04:03, Julien Pauli jpa...@php.net wrote: On Wed, Apr 10, 2013 at 6:52 PM, Pierre Joye pierre@gmail.com wrote: On Wed, Apr

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

Including 5.3 and 5.4 ?? Pierrick On 11 April 2013 14:12, Pierre Joye pierre@gmail.com wrote: On Thu, Apr 11, 2013 at 4:54 PM, Pierrick Charron pierr...@adoy.net wrote: If you decide to remove it for 5.5 RC, tell me and I'll merge this branch https://github.com/adoy/php-src/tree

Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers

Hi I don't think we should remove curlwrappers from 5.5. I do agree that this is not yet stable and ready to push as non experimental, but since we plan to release 5.5 soon I don't think removing it right now is worth it. I started some time ago to maintain the curl extension. I focused mainly

Re: [PHP-DEV] Dropping requirement for `function` keyword for methods in classes/interfaces/etc

Protip: use an IDE. The IDE that i'm using may search for something like function \w to find all the functions of my code. So I may have to wait for a new update of the IDE to be able to use the index, and I also may have to pay to get the update of my IDE. So why would I want all this if I can

Re: [PHP-DEV] [RFC] Allow trailing comma in function call argument lists

+1 On 19 February 2013 07:06, Sara Golemon poll...@php.net wrote: Opening RFC to allow trailing comma in function call argument lists https://wiki.php.net/rfc/trailing-comma-function-args -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

Re: [PHP-DEV] Zend Optimizer+ Source Code now available

That's a good idea :) I'm also in On 13 February 2013 09:51, Zeev Suraski z...@zend.com wrote: As per Derick’s idea, we can arrange a webinar for those interested in better understanding how it works.

Re: [PHP-DEV] Zend Optimizer+ Source Code now available

Hi, I tried to install the ZendOptimizer+ provided earlier today but wasn't able to make it work. I compiled it with success but when I looked at the phpinfo(); I had this : Opcode Caching Disabled Optimization Enabled Startup Failed no value I'm using the apache2handler (MPM Worker -

Re: [PHP-DEV] Re: [VOTE] CURLFile uploading API

Hi Stas, I'm not against it but, just being curious, what are those security reasons ? Thanks Pierrick On 28 January 2013 15:01, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! I've started a vote on CURLFile RFC: https://wiki.php.net/rfc/curl-file-upload#vote Please vote. Looks

Re: [PHP-DEV] Re: [VOTE] CURLFile uploading API

Thanks for the example. Even if it's not frequent I agree that it doesn't cost much to prevent this issue Pierrick On 1 February 2013 13:04, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! I'm not against it but, just being curious, what are those security reasons ? If you ever accepted

Re: [PHP-DEV] [RFC] Fixing insecure cURL file uploading

Hi Stas, What's the status of this fix ? Thanks Pierrick On 8 January 2013 04:23, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! Looks good to me, just it could be great to add a new cURL option at the same time to disable the '@' usage so that someone working with the new ext/curl

Re: [PHP-DEV] [RFC] Fixing insecure cURL file uploading

Great :) Thanks for the update On 17 January 2013 15:35, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! What's the status of this fix ? The pull is in the RFC, so I planned to do the vote on Monday and then get it merged if nobody objects. -- Stanislav Malyshev, Software Architect

Re: [PHP-DEV] - True Annotations

Annotations can be nested so in this case [Foo([BAR])] there is a big ambiguity and we can not determine if [BAR] is an array with the BAR constant in it or an annotation. Pierrick On 9 January 2013 05:53, Clint Priest cpri...@zerocue.com wrote: In none of those scopes would [ ] be a parsing

Re: [PHP-DEV] - True Annotations

# is an alternative syntax for comments On 9 January 2013 08:27, Nikita Nefedov inefe...@gmail.com wrote: #Foo(#Bar()) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] [RFC] Reflection annotations reader

Hi, I agree with you on this point, we should not introduce any new feature if there is no way to deal with largely used extensions like apc, xdebug or maybe others. The provided implementation is not supposed to be final (syntax or internal implementation) and I'm sure there are many

Re: [PHP-DEV] [RFC] Reflection annotations reader

On 8 January 2013 03:55, Stas Malyshev smalys...@sugarcrm.com wrote: On the contrary, plenty of implementations means there's a need in this functionality, and it might be a good idea to have one standard implementation if it can cover like 80% of use cases. I agree, there is a need in this

Re: [PHP-DEV] [RFC] Reflection annotations reader

I do use PHP Unit and also Doctrine which uses annotations. And I know that today because there is no native annotations, the implementation use docblocks so I can not remove them :) But still if I did not know anything about PHP and that someone was talking to me about comments, I would expect my

  1   2   >