Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52203
Return-Path: <lars.schultz@toolpark.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 8146 invoked from network); 10 May 2011 08:16:27 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 10 May 2011 08:16:27 -0000
Authentication-Results: pb1.pair.com header.from=lars.schultz@toolpark.com; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=lars.schultz@toolpark.com; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain toolpark.com from 195.49.42.12 cause and error)
X-PHP-List-Original-Sender: lars.schultz@toolpark.com
X-Host-Fingerprint: 195.49.42.12 mail1.screenlight.ch  
Received: from [195.49.42.12] ([195.49.42.12:55711] helo=mail1.screenlight.ch)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 29/31-01064-A54F8CD4 for <internals@lists.php.net>; Tue, 10 May 2011 04:16:27 -0400
Received: from [192.168.1.112] ([192.168.1.112])
	(authenticated user lars.schultz@toolpark.com)
	by mail1.screenlight.ch (Kerio Connect 7.0.2 patch 1)
	(using TLSv1/SSLv3 with cipher AES256-SHA (256 bits))
	for internals@lists.php.net;
	Tue, 10 May 2011 10:16:22 +0200
Message-ID: <4DC8F459.7000405@toolpark.com>
Date: Tue, 10 May 2011 10:16:25 +0200
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: internals@lists.php.net
References: <BANLkTinO0h7020fs+PLjM0fUmMjQXoTsyw@mail.gmail.com>	<BANLkTim8p7A5+svvjZw6rc_KE+tBMnOsjw@mail.gmail.com>	<4DC826B1.4090806@lerdorf.com>	<BANLkTikpLY+AntSrNi91rzGNZi4FkPrSwA@mail.gmail.com>	<4DC82A36.8090604@lerdorf.com>	<BANLkTi=aLVw8KqOV_jb9dBm=XqX6TqTVwA@mail.gmail.com>	<4DC83401.2090202@sugarcrm.com>	<BANLkTiniayhZ+8CRQjPFBDLOBu=E7UUv=A@mail.gmail.com>	<BANLkTimvE1nE+UOv+8hUaPiyfozn3PgU3Q@mail.gmail.com>	<BANLkTinfEFsiSWOi3RgjZ4-6QeNjRVMwTQ@mail.gmail.com>	<4DC8D122.3050507@lsces.co.uk>	<BANLkTim1euVOKXxLc3FdhJAywqnPHDkbwg@mail.gmail.com>	<BANLkTi=AxkZf_jMUJ0MaRREVX9t33Ex0Zw@mail.gmail.com>	<4DC8F125.2010503@toolpark.com> <BANLkTi=aUL0UNUK9tF9cz8Nsm3z8AB0XQQ@mail.gmail.com>
In-Reply-To: <BANLkTi=aUL0UNUK9tF9cz8Nsm3z8AB0XQQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] annotations again
From: lars.schultz@toolpark.com (Lars Schultz)

Am 10.05.2011 10:10, schrieb Jordi Boggiano:
> I think the main reasons are standardization of the syntax and
> performance of the parsing. At the moment everyone has to cache the
> stuff because hitting the tokenizer every time is quite expensive.
If implemented within PHP the existing opcode-caches could work wonders 
on this.

> Annotations are not code, but more like metadata to tell the
> surrounding libraries how to work best with a piece of code.
What is code?;) What's the Problem with having meta-data within PHP-Code?

> I think your example shows very well why annotations are good, it's
> much more concise.
But my example is much more verbose (which is good in my view), uses 
common syntax and is very flexible! It gives you the whole power of PHP 
instead of a semi-language (no offense).