Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64733
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <d99abc9fe13866dc9e948b7a89b21feb@mohiva.com>
References: <50ED4C18.3090806@zerocue.com> <9f792e7e11c481c5f4c62ce69ae216b6@mohiva.com>
 <CANVTSm6hs0L-a0b4t3pj4RFjx8LZVHf3jWkkSqKG9gr-dpSEEg@mail.gmail.com> <d99abc9fe13866dc9e948b7a89b21feb@mohiva.com>
Date: Wed, 9 Jan 2013 14:13:23 +0200
Message-ID: <CANVTSm5upbRajmyekfqyZMqtFbQXW3c_MDT2W0VBWkJEagM3Aw@mail.gmail.com>
To: Christian Kaps <christian.kaps@mohiva.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04447e015d1d7b04d2d9fe10
Subject: Re: [PHP-DEV] - True Annotations
From: g.b.yahav@gmail.com (Yahav Gindi Bar)

--f46d04447e015d1d7b04d2d9fe10
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 9, 2013 at 2:09 PM, Christian Kaps <christian.kaps@mohiva.com>wrote:

> Am 09.01.2013 13:03, schrieb Yahav Gindi Bar:
>
>> On Wed, Jan 9, 2013 at 1:57 PM, Christian Kaps <christian.kaps@mohiva.com
>> >**wrote:
>>
>>  Hi,
>>>
>>>
>>>  I agree here, I think the above, if possible would be best.  In my
>>>
>>>> mind annotations should proabably be limited in scope to class
>>>> declarations and thus only before a class keyword, before a property
>>>> or method declaration.
>>>>
>>>> In none of those scopes would [ ] be a parsing issue I believe...
>>>>
>>>> The one case would be at the beginning of a class, but if simply
>>>> added something such as:
>>>> [:SomeAttribute(xyz,abc),****SomeAttribute2]
>>>>
>>>>
>>>> It could never be confused with short array syntax and is still brief.
>>>>
>>>>
>>> I think when implementing real annotations, then it should be possible to
>>> declare arrays in it. So I think the square brackets don't work.
>>> [Foo([1,2,3])]
>>>
>>> Cheers,
>>> Christian
>>>
>>> --
>>> PHP Internals - PHP Runtime Development Mailing List
>>> To unsubscribe, visit: http://www.php.net/unsub.php
>>>
>>> But the colon prefix won't cover this case?
>>>
>>
>> You can, as I've mentioned in my post at the doc-block parser discussion,
>> use a keyword inside the brackets to symbolize annotation, for example
>>
>> [metadata: Key]
>> [metadata: MaxLength(10)]
>> [metadata: Relations(["foo", "bar", "baz"])]
>> public $id;
>>
>
> Then rather [@Foo([1,2,3])] if it's possible!
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> Yeah, that's cool. To be honest, I took that idea from C# which has, for
example (Quoted from standard template AssemblyInfo.cs):

// Version information for an assembly consists of the following four
values:
//
//      Major Version
//      Minor Version
//      Build Number
//      Revision
//
// You can specify all the values or you can default the Revision and Build
Numbers
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]

--f46d04447e015d1d7b04d2d9fe10--