Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83821
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.25 cause and error)
Message-ID: <54EE2F43.3020108@garfieldtech.com>
Date: Wed, 25 Feb 2015 14:23:31 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CA+9eiLsxSpbdaa7Bpci2PRXQMRkTUiwZphjQYv2iDyXLUhrMow@mail.gmail.com> <02a101d04af9$507484f0$f15d8ed0$@php.net> <CAFp73XvcT5usUM6xJFwZ2dD9ARW+wRnygf0X-kj+hWe_8KQZ7g@mail.gmail.com> <CA+9eiLtXd3_3TwU84HCcMeHqF_9toC7eH6j8bY63h4z=5gJrnw@mail.gmail.com> <CAEPJduk0BV4JsF7r3k-HCXD2Ec3rDLaqF8aMbVCnLfXo4BPCgg@mail.gmail.com> <02ff01d04b72$abae34a0$030a9de0$@php.net> <CA+9eiLu19ewy6vjR+Cf00rd3TFnUyG-0rKZWjb3aift+fjheRg@mail.gmail.com> <032801d04b8d$8ff3dce0$afdb96a0$@php.net> <CA+9eiLsRK6DQGPnY3B=uvcEYfF_gaSQ5OZUesf6+qe60m7t66w@mail.gmail.com> <CAFp73XtrJMLpfzJHQp+tGFWiqJ0HVVwakEXQiMFWkaVZANRxkg@mail.gmail.com> <CAB6YZuxcU+nfvd=WkM-CYNcO=g1yGxALrCPSP6Y2-p-k9PNenw@mail.gmail.com> <CAEPJdu=JEwAmh+i5f+OHbU1Au0LqDAmuh5gJorta+N4MwZs6_g@mail.gmail.com> <CAB6YZuwY-TB0VsPqEJ=r2eD=3BVhBM8xoJo_Y9zQ+arROr8cgA@mail.gmail.com> <54ED4F3E.3060901@garfieldtech.com> <CAF8gL+7EjWTo44E7uZT-c4YdZ2=ph1tY2w5KKc96aDt2bsXNAQ@mail.gmail.com>
In-Reply-To: <CAF8gL+7EjWTo44E7uZT-c4YdZ2=ph1tY2w5KKc96aDt2bsXNAQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Annotations in PHP7
From: larry@garfieldtech.com (Larry Garfield)

On 2/25/15 5:45 AM, Peter Holák wrote:
> One thing to consider when annotations are classes is whether using an
> annotation should make the annotated class depend on the annotation
> classes it uses. In other words, would a missing annotation class
> produce an error? It doesn't in Java (at runtime, see
> http://stackoverflow.com/a/3567969) and I think they made the right
> choice on that (although you can't compare this directly to PHP due to
> the nature of compilation in Java, and it is still a compile error
> there).
>
> Consider an entity class with Doctrine mappings in annotations. This
> class is still perfectly usable on its own without this persistence
> information (assuming you don't care about database persistence in
> such situations), just as it would be if the mapping information was
> in XML/YAML files instead. I don't think Doctrine should be a hard
> dependency of such a class.
>
> Of course the code that _reads_ the annotations still depends on the
> annotation classes it cares about.
>
> 2015-02-25 5:27 GMT+01:00 Larry Garfield <larry@garfieldtech.com>:
>> On 02/21/2015 03:35 PM, Pavel Kouřil wrote:
>>>
>>>
>>> I know you could wrap it in your code, but that would still mean there
>>> would probably be multiple implementations of Annotations in the
>>> "wild", instead of a good complete functionality in the language
>>> itself.
>>>
>>> I know PHP is not primarily an OOP language, but Annotations IMHO make
>>> sense as classes, so I don't see any reason why would it be bad to
>>> make them in that way. Also, making Annotations be classes won't
>>> magically turn PHP into a primarily OOP language?
>>>
>>> Regards
>>> Pavel Kouřil
>>
>>
>> If you look at the major projects and code in the wild, PHP is a primarily
>> OOP language and has been for years.  It's multi-paradigm but OOP is the
>> dominant style in the wild today.
>>
>> And I think mapping annotations to classes is a fine idea, as it means I can
>> very easily document what a given annotations is for (it's a class, document
>> the class), extend it, and build meaningful functionality and defaults using
>> an already well-known syntax and convention.
>>
>> --Larry Garfield

Consistent top/bottom posting please... this is a bottom-posting-thread.

And yes, I agree that we shouldn't make absence of an 
annotation-referenced class an error until the annotation is actually 
read.  Until the annotations is used, the class shouldn't be loaded so 
it's ignored.

--Larry Garfield