Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69717 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28595 invoked from network); 21 Oct 2013 08:01:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2013 08:01:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.171 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.128.171 mail-ve0-f171.google.com Received: from [209.85.128.171] ([209.85.128.171:33396] helo=mail-ve0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 82/DB-44908-57FD4625 for ; Mon, 21 Oct 2013 04:01:57 -0400 Received: by mail-ve0-f171.google.com with SMTP id c14so3709894vea.2 for ; Mon, 21 Oct 2013 01:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=UvngtuSgdHy2y0PkVY+98mX/Z6c+ZH5nqAyC/kACU0Q=; b=wTVwlyrbm+BvRkOlvvKku+FWK0pnAzvlHCbd57GXTkI0xrOIaNQoFsMDA5Bk6dCb3n ich+hr+DhtQXz8w+6k8XpXnSITml+oor/0g1xSxO62hRBuflqEmHH+jHagw7J1NxaapN MXbrbfGMHK+2BvbofpsEP+ULm0aGAuwy26a/dmGqmvtnApEA1L1yggqzMIIiS1WJVlQI ZWsX3YYWpVep8+pbboDZ631zkP1m2DUyFh2WW1RVVc3Sz5cC0URbCjv8rcUnr1epV6hS KNW1Kea8zlq1DMfjkt8/qbfxsXHFpT83fd8ygk7Ve5Mq70mvx1Zpr9tZ9Hpn8D7QAFvh dmeA== X-Received: by 10.220.105.199 with SMTP id u7mr10223254vco.1.1382342515056; Mon, 21 Oct 2013 01:01:55 -0700 (PDT) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.220.73.197 with HTTP; Mon, 21 Oct 2013 01:01:14 -0700 (PDT) In-Reply-To: <526488C1.8020400@php.net> References: <3D.BC.23638.84CA1625@pb1.pair.com> <000301cecd1b$9aa133f0$cfe39bd0$@tutteli.ch> <526488C1.8020400@php.net> Date: Mon, 21 Oct 2013 10:01:14 +0200 X-Google-Sender-Auth: 9_M5Adw4-ge17qc2yvZGzhPqOfA Message-ID: To: Joe Watkins Cc: PHP Internals , Ferenc Kovacs Content-Type: multipart/alternative; boundary=047d7b343eca91659f04e93bb29e Subject: Re: [PHP-DEV] RFC: Expectations From: jpauli@php.net (Julien Pauli) --047d7b343eca91659f04e93bb29e Content-Type: text/plain; charset=ISO-8859-1 On Mon, Oct 21, 2013 at 3:52 AM, Joe Watkins wrote: > On 10/20/2013 12:15 AM, Ferenc Kovacs wrote: > >> On Sun, Oct 20, 2013 at 12:36 AM, Robert Stoll wrote: >> >> Heya, >>> >>> I do not know how much it concerns this RFC but I came across the >>> following >>> page about an extension named "Expect" when I was searching for RFC >>> Expect >>> with google. >>> http://php.net/manual/en/book.**expect.php >>> >>> I suppose there would be a name clash between the extension and the new >>> expect keyword. I do not know how internals usually deal with such >>> problems, >>> especially if it is within an extension, but I am sure someone will know >>> it. >>> >>> Cheers, >>> Robert >>> >>> >>> it was discussed on irc, there is not problem here, because the ext name >> and the function name can't clash, and the ext doesn't have a function >> with >> the name of expect, so everything is fine afaik. >> >> > Rasmus has pointed out that there is an expect:// stream wrapper. > > So looks like we need a new name ?? Ideas ?? Why ? The stream wrapper is always used in a string, so there is no parsing problem about the "expect" keyword. Am I missing something ? Julien.Pauli --047d7b343eca91659f04e93bb29e--