Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58847 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 73872 invoked from network); 11 Mar 2012 22:10:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Mar 2012 22:10:27 -0000 Authentication-Results: pb1.pair.com header.from=tom@punkave.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tom@punkave.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.210.170 as permitted sender) X-PHP-List-Original-Sender: tom@punkave.com X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:47188] helo=mail-iy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 43/D7-24751-3D22D5F4 for ; Sun, 11 Mar 2012 17:10:27 -0500 Received: by iaeh11 with SMTP id h11so6668719iae.29 for ; Sun, 11 Mar 2012 15:10:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=I+yULCeuynm2hoSkxPrjx7c87/u8BzcuCHWZL0LKg34=; b=P3X1rQvvoJ5w739kmro6Quc/FzRTlPijTUyK41qqyS3AvxKBJUeD1XRst1xs8T4VOL tYbze1owXvbOj9oi1zJcQ5ybvimom0/n+szvPcOjY5AUA+7MAqWG/laZwhcQh5eqQN/k dnO6N597NIqPUa2Kl6tucd1dEoZ+Eju9RmVFORMjknpMLI5WfiudAwfSlnxPjiQx1wf7 BpzFLve5qvw4SYrtYP3we0ZUUqYOA8UA72mW8Iy8zq/95HW83TrgrziRHsNym0J2eCpM QWmrA3JDm2kvM0HUl/1yBnPSCVDAuIT871wt7by+LPGIJsnxnDEc3riR93xDlJxsY7eO iq4Q== MIME-Version: 1.0 Received: by 10.50.190.167 with SMTP id gr7mr189968igc.8.1331503825055; Sun, 11 Mar 2012 15:10:25 -0700 (PDT) Received: by 10.231.152.85 with HTTP; Sun, 11 Mar 2012 15:10:25 -0700 (PDT) In-Reply-To: References: <4F5C5540.8010204@sugarcrm.com> Date: Sun, 11 Mar 2012 18:10:25 -0400 Message-ID: To: Pierre Joye Cc: Stas Malyshev , Pierrick Charron , Internals Content-Type: multipart/alternative; boundary=f46d0447850f8270f904bafee47f X-Gm-Message-State: ALoCoQkwOAK8zmeurxdiMR3Y21ifSaM9xAl5nvhbX920/nR7uJjwQdkSlU5k5NuBVS9Ulz5mX9Nu Subject: Re: [PHP-DEV] Upgrade cURL extension From: tom@punkave.com (Tom Boutell) --f46d0447850f8270f904bafee47f Content-Type: text/plain; charset=ISO-8859-1 Sigh, I could have edited that better, but I think the apology came across (: This is still a thing worth fixing. On Sun, Mar 11, 2012 at 6:09 PM, Tom Boutell wrote: > I do see now that at curl did introduce the @ craziness. So it is unfair > of me to single out PHP for introducing it. I'm not sure if the @ syntax is > a sneaky feature of the standard C API, but it's definitely a sneaky > feature of the command line utility. > > I did include a comment there when I first opened that bug report, > proposing a more appropriate and sustainable interface. Documentation > changes would make it possible to avoid the problem by looking carefully > for strange "gotchas" in the fine print - but not to actually submit a > value starting with a @, if, y'know, I wanted to do something crazy-nutty > like send arbitrary data legal in any other form submission (: > > Apologies for hijacking the discussion. > > The '@' business does not come from libcurl. Native C libcurl > > On Sun, Mar 11, 2012 at 3:38 PM, Pierre Joye wrote: > >> hi Tom, >> >> For one, it is mapped to the libcurl constants and behavior. >> >> Also this but report contains clear comment about this issue being a >> documentation problem, contribution welcome :) >> >> If you consider it as something that should be changed, then please >> feel free to add a comment there as well, or a patch :) >> >> But that's not really what we discuss here but the new code proposed >> by Pierrick. >> >> Cheers, >> >> On Sun, Mar 11, 2012 at 4:22 PM, Tom Boutell wrote: >> > I'd sure like a PHP extension that didn't have this obvious and nasty >> bug: >> > >> > https://bugs.php.net/bug.php?id=46439 >> > >> > On Sun, Mar 11, 2012 at 3:33 AM, Stas Malyshev > >wrote: >> > >> >> Hi! >> >> >> >> >> >> I wanted to make this new version available in PHP5.4 but >> >>> unfortunately I did finish my work when it was already in RC phase. >> >>> The question now is should we include this new version in PHP5.4.1 or >> >>> should we wait for PHP 5.5/6/7 or whatever PHP next will be. There is >> >>> no feature break (AFAIK) so all the previous code should work as >> >>> expected. You'll find the list of new features attached and the last >> >>> code in the trunk branch. >> >>> >> >> >> >> Can't you make it also available as pecl extension, which could be >> built >> >> on 5.4? This way people could enjoy the benefits of your work without >> >> stable branch being disrupted and BC problems raised. >> >> >> >> -- >> >> Stanislav Malyshev, Software Architect >> >> SugarCRM: http://www.sugarcrm.com/ >> >> (408)454-6900 ext. 227 >> >> >> >> >> >> -- >> >> PHP Internals - PHP Runtime Development Mailing List >> >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> >> >> >> > >> > >> > -- >> > Tom Boutell >> > P'unk Avenue >> > 215 755 1330 >> > punkave.com >> > window.punkave.com >> >> >> >> -- >> Pierre >> >> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org >> > > > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com > > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com --f46d0447850f8270f904bafee47f--