Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30759 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93399 invoked by uid 1010); 11 Jul 2007 02:11:31 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 93383 invoked from network); 11 Jul 2007 02:11:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2007 02:11:30 -0000 Received: from [127.0.0.1] ([127.0.0.1:21089]) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ECSTREAM id 84/7E-63792-1F234964 for ; Tue, 10 Jul 2007 21:31:29 -0400 Authentication-Results: pb1.pair.com smtp.mail=evertpot@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=evertpot@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.182 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: evertpot@gmail.com X-Host-Fingerprint: 64.233.166.182 py-out-1112.google.com Received: from [64.233.166.182] ([64.233.166.182:63777] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A8/BD-63792-50F24964 for ; Tue, 10 Jul 2007 21:14:46 -0400 Received: by py-out-1112.google.com with SMTP id f31so5057453pyh for ; Tue, 10 Jul 2007 18:14:42 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=RfiJifgRodIt5qdksK7e5OGzu1rh2wtg637rQfssrc2SI7XvDP6lOV96y4hAEOZhxKisTOd3RXl50FQ6Z0pdEKIEIe4pr3q/JDGy6TelckSz2j4CUCz2JwhIi0VflUEiOj1ugNVVIrIWr2Q0F+o1EyHd36NkKGtJ3R89BBxaUIo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=L4+BVAGWXUcG0x6cryi4PcYnIrw+wHQe2YWZJvm26qE+9I5DU6CpU4p8Ncak4+FaAAdIbRLApwozWt3Rwd5Ntmq4K11BJiSCoBoGce8GeK0v+uPOKSgUu9sUEwizynOVDj2S92ztLdkDacL6er9rrSR3R6cNr+TZHnNa54r37pY= Received: by 10.65.214.19 with SMTP id r19mr7857910qbq.1184116482577; Tue, 10 Jul 2007 18:14:42 -0700 (PDT) Received: from evertbook.local ( [74.98.199.234]) by mx.google.com with ESMTP id e15sm7569879qbe.2007.07.10.18.14.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Jul 2007 18:14:40 -0700 (PDT) Message-ID: <46942A82.90909@rooftopsolutions.nl> Date: Tue, 10 Jul 2007 20:55:30 -0400 User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Andi Gutmans CC: Antony Dovgal , Andrei Zmievski , Stas Malyshev , internals@lists.php.net, system@php.net References: <1181829227.3478.3.camel@localhost.localdomain> <34654.216.230.84.67.1183064088.squirrel@www.l-i-e.com> <54557.78.61.224.253.1183098089.squirrel@avilys.eik.lt> <4684BB91.4070507@zend.com> <2169.24.1.37.132.1183693664.squirrel@www.l-i-e.com> <1183699755.14343.5.camel@johannes.nop> <7d5a202f0707060224oa64dfeaw2c7ee17a735648f9@mail.gmail.com> <468E1158.2030900@lerdorf.com> <468E13C6.1070109@pooteeweet.org> <468E2009.9000703@zend.com> <468E7180.3020709@zend.com> <468E7256.10905@zend.com> <4692B1A3.1000808@zend.com> <698DE66518E7CA45812BD18E807866CE647897@us-ex1.zend.net> <698DE66518E7CA45812BD18E807866CE64794E@us-ex1.zend.net> <4693B66C.4000908@rooftopsolutions.nl> <698DE66518E7CA45812BD18E807866CE647A32@us-ex1.zend.net> In-Reply-To: <698DE66518E7CA45812BD18E807866CE647A32@us-ex1.zend.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: Evert Pot - Rooftop Solutions Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6? From: evert@rooftopsolutions.nl (Evert | Rooftop) Andi Gutmans wrote: > I think the sooner the better as it's valuable information for the dev > team. > It'd probably be a good idea to have a Wiki where we can document issues > that/common use-cases which are encountered. > Maybe we should have a Wiki on one of the php.net servers for such > purposes? > Andi > > Is anyone aware of a list with a, say top 10 PHP applications? When such a wiki is setup, how would you suggest to write such documents.. At least a generic guide would be good (e.g.: common pitfalls) Should I be documenting the per-project specifics as well? Evert