Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69596 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88996 invoked from network); 17 Oct 2013 05:56:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2013 05:56:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=bof@bof.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=bof@bof.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender) X-PHP-List-Original-Sender: bof@bof.de X-Host-Fingerprint: 80.242.145.70 mars.intermailgate.com Received: from [80.242.145.70] ([80.242.145.70:41277] helo=mars.intermailgate.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 96/10-22512-00C7F525 for ; Thu, 17 Oct 2013 01:56:16 -0400 Received: (qmail 28921 invoked by uid 1009); 17 Oct 2013 07:56:13 +0200 Received: from 209.85.220.177 by mars (envelope-from , uid 89) with qmail-scanner-1.25-st-qms (clamdscan: 0.96.2/17965. spamassassin: 3.3.1. perlscan: 1.25-st-qms. Clear:RC:1(209.85.220.177):. Processed in 0.073615 secs); 17 Oct 2013 05:56:13 -0000 X-Antivirus-MYDOMAIN-Mail-From: bof@bof.de via mars X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:1(209.85.220.177):. Processed in 0.073615 secs Process 28911) Received: from mail-vc0-f177.google.com (gmail@bof.de@209.85.220.177) by mars.intermailgate.com with RC4-SHA encrypted SMTP; 17 Oct 2013 07:56:13 +0200 Received: by mail-vc0-f177.google.com with SMTP id ib11so562888vcb.36 for ; Wed, 16 Oct 2013 22:56:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OIY1T7hWfH+QOfWRvs5UBJAYi3Pb1K4kujdClYvR87g=; b=OBz+UI+mhjima4/9oMADLbkptk53rmpdrScTXMOzDJdnCcsuUOhhe98Ld1ezyM4YjB kJKhTZel/XJmykZH/rduDEkFBFQw9L4Gih6Ff2uYd6R6rHCY/6q4CQDxoiRsku3/sJ9e zoK1R8Q/i1ZqB6r1aXpriY0kAzgWguvJLdhomGGaLq1XltkAL0tpZ8Ll0THYnfWuGs1/ 6BPjdeHIPIVUub3K28sAsqkw+EeNm2+PJcBMyLVFyH5NkKutEcUAySUuWFdJDmVIghLN S0KrFaJdQ09fAW0TvDiv+yu1wU7DQTrNX5yLrTWJ/grqtSQ0lxaxcRh1dJcP9IexV7T3 MUJw== MIME-Version: 1.0 X-Received: by 10.58.207.15 with SMTP id ls15mr5530429vec.17.1381989371507; Wed, 16 Oct 2013 22:56:11 -0700 (PDT) Received: by 10.52.185.102 with HTTP; Wed, 16 Oct 2013 22:56:11 -0700 (PDT) Received: by 10.52.185.102 with HTTP; Wed, 16 Oct 2013 22:56:11 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Oct 2013 07:56:11 +0200 Message-ID: To: Bob Weinand Cc: internals Content-Type: multipart/alternative; boundary=047d7b6dc6ee927e9204e8e97909 Subject: Re: [PHP-DEV] [RFC] Keywords as identifiers From: bof@bof.de (Patrick Schaaf) --047d7b6dc6ee927e9204e8e97909 Content-Type: text/plain; charset=ISO-8859-1 Hi, regarding the typehint issue mentioned in the RFC, I feel that it would be more consistent to handle that like the default/else goto label issue, i.e. disallowing class or interface names "array" and "callable" in the first place (and keeping the current behaviour of those when used as typehints). Otherwise, I would vote "yes" if I had voting rights :) best regards Patrick --047d7b6dc6ee927e9204e8e97909--