Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50717 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 7481 invoked from network); 30 Nov 2010 09:49:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2010 09:49:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=gwynne@darkrainfall.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=gwynne@darkrainfall.org; sender-id=unknown; domainkeys=bad (key type) Received-SPF: error (pb1.pair.com: domain darkrainfall.org from 208.97.132.202 cause and error) DomainKey-Status: bad (key type) X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: gwynne@darkrainfall.org X-Host-Fingerprint: 208.97.132.202 caiajhbdccac.dreamhost.com Linux 2.6 Received: from [208.97.132.202] ([208.97.132.202:60009] helo=homiemail-a10.g.dreamhost.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7C/D4-01713-4C8C4FC4 for ; Tue, 30 Nov 2010 04:49:57 -0500 Received: from homiemail-a10.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a10.g.dreamhost.com (Postfix) with ESMTP id C5FF428005C; Tue, 30 Nov 2010 01:49:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=darkrainfall.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= darkrainfall.org; b=ENf9EPjhZOQDtF43WwQuiGV+TL6mCy9VUDPslc71Shqj ktymh9UgvXyX8yxhWkI3G/wAFwD7GN+nyLoYlcHLAvHBo+wwcKSTMCGjVTUWQl4P E1lZMjs4mZYgjklpDxhjaYVMT02nCClP3TUPVqlZ5Yce8INYMQWGpmWvrBa4V1Y= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=darkrainfall.org; h= subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= darkrainfall.org; bh=wzo/e1HZdoIAY3ai5mioasqT4U4=; b=r4hvjLcxYu8 IWPV9tj0XCAxBg/a8tmxm3RIjkzeihk/PnsECmfC0QZvfPLatQL9S8J/mpCf2iZX I63CcG4oEiG3nId8ZHJG/f5/nGQ10it5ioZdpkeQL/AjTF5NVQJ4WNyaQJCJvcQt I2QfYLeqaHv5nislX5NL3GGA0sZgMB/8= Received: from [192.168.1.3] (pool-173-48-161-16.bstnma.fios.verizon.net [173.48.161.16]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: gwynne@darkrainfall.org) by homiemail-a10.g.dreamhost.com (Postfix) with ESMTPSA id 499A4280063; Tue, 30 Nov 2010 01:49:52 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii In-Reply-To: Date: Tue, 30 Nov 2010 04:49:52 -0500 Cc: PHP internals Content-Transfer-Encoding: 7bit Message-ID: References: <1290879624.7033.826.camel@guybrush> To: Arvids Godjuks X-Mailer: Apple Mail (2.1082) Subject: Re: [PHP-DEV] Re: RFC: Making T_FUNCTION optional in method declarations From: gwynne@darkrainfall.org (Gwynne Raskind) On Nov 30, 2010, at 4:24 AM, Arvids Godjuks wrote: > Personally, as a user-land developer, I'm against it, so -1. > function keyword is the only sane way to quickly find a function > definition in lots of code. Not always IDE's are able to fully > understand the interconnections in frameworks and point by CTRL + > Click me to the function definition, not to say that in many cases you > just don't have that IDE available right now and right here. > Now it's quite easy to make a search on a folder recursively - just > enter "function blah" and here you go - one entry with the function > definition. Try that with the function/method name without the > "function" keyword, good luck with going through tons of entries. > > I deal with typing the whole "public/private function blabla() {" by > defining a auto complete shortcut like "prfnc => space => private > function |(){" where | is cursor. > > Please keep it KISS way. Language should evolve for sure, but some > things are not just worth sacrificing the verbosity even if it means > cuts typing some of the most common keywords in the language and can > be perfectly done keeping the BC. > > P.S. Personally I will prohibit my developers to use the short syntax > without the "function" keyword. Agreed. -1 here also. -- Gwynne