Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69714 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4663 invoked from network); 21 Oct 2013 01:52:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2013 01:52:07 -0000 X-Host-Fingerprint: 80.4.21.210 cpc22-asfd3-2-0-cust209.1-2.cable.virginmedia.com Received: from [80.4.21.210] ([80.4.21.210:2214] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/48-44908-6C884625 for ; Sun, 20 Oct 2013 21:52:06 -0400 To: internals@lists.php.net,Ferenc Kovacs Message-ID: <526488C1.8020400@php.net> Date: Mon, 21 Oct 2013 02:52:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 References: <3D.BC.23638.84CA1625@pb1.pair.com> <000301cecd1b$9aa133f0$cfe39bd0$@tutteli.ch> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 80.4.21.210 Subject: Re: [PHP-DEV] RFC: Expectations From: krakjoe@php.net (Joe Watkins) 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 ?? Cheers Joe