Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68175 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6378 invoked from network); 18 Jul 2013 23:09:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jul 2013 23:09:10 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.91 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.91 smtp91.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.91] ([108.166.43.91:46372] helo=smtp91.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/11-34315-49578E15 for ; Thu, 18 Jul 2013 19:09:09 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 9F16014009A; Thu, 18 Jul 2013 19:09:06 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 45E4C1400A5; Thu, 18 Jul 2013 19:09:06 -0400 (EDT) Message-ID: <51E87591.8010008@sugarcrm.com> Date: Thu, 18 Jul 2013 16:09:05 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: =?KOI8-R?Q?=E2=CF=C7=C4=C1=CE_=EB=D5=DA=C5=CD=C1?= CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] SPL Binary Tree, Graph From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I would like to ask you what is your opinion about implementing Binary Tree > and Graph data structures in SPL in addition to existing ones? IMHO it Sure, why not? But I'd suggest first proposing the API for the classes in the form of the RFC (https://wiki.php.net/rfc) and explanation what is their goals and what they would allow to do better than it is done before, then collecting the feedback and proceeding from there to implementation if the feedback proves that the community is supportive of this. > would be great because that will prevent from inventing a wheel all the > time, and prove that PHP is full featured language like C#, Java, ... I don't think after 18 years of history of being used by millions of developers and being one of the most widely used open source software projects we need to "prove" to anybody that PHP is a full featured language, but improving PHP to serve the users better is always the goal. So if you think you can help in making PHP better - great! -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227