Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82058
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54D4FFA4.3010703@birkholz.biz>
References: <CA+9eiLuNjTa8JzBgnZE5iuv5BZ4Kw4Ehk1ivxPUetNSmZ43JMw@mail.gmail.com>
 <54D37D41.2030706@hoa-project.net> <CAGa2bXa_E27ZK89j-C3c0-Kj8pDY4EN_8U6SQC2K19SNm46wqg@mail.gmail.com>
 <54D470FA.6000303@hoa-project.net> <CAGa2bXaGE3QWjGxvRadLG0btA5wd1u5bZ=AAo6WQHE_Uek8iaw@mail.gmail.com>
 <02d301d041f3$0c5f3990$251dacb0$@tekwire.net> <CAGa2bXafsdmTPutaYP_oyX9CbjaRcJyqk0r3_v-ud=yCiQT_SA@mail.gmail.com>
 <CAGa2bXZnBWoL7NogbQCrfy-80G7xWoD_EJT3KH3v9aPiJ68Csw@mail.gmail.com>
 <031501d04217$b393bff0$1abb3fd0$@tekwire.net> <CA+9eiLvfn570PY+9yxvN8nDODyvXwFKE--LaYOm5-1RLLd7DvA@mail.gmail.com>
 <CAFp73XsSEBubkVXeXary2tLbxDoAZntdZz5N6Y1x0p7bGq_6Rg@mail.gmail.com>
 <CA+9eiLtFpsg1usWTdTtGnkF9cp+ix2n3mMUtUYq8tOEn3AGtZw@mail.gmail.com> <54D4FFA4.3010703@birkholz.biz>
Date: Fri, 6 Feb 2015 13:21:47 -0500
Message-ID: <CAFp73XsmaMRdyQmyyjgsOJ9iPgEWwJnkkeufuPD1zS3RXRL3+g@mail.gmail.com>
To: Dennis Birkholz <dennis@birkholz.biz>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf3043530a8be842050e6f7fc2
Subject: Re: [PHP-DEV] Design by Contract
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--20cf3043530a8be842050e6f7fc2
Content-Type: text/plain; charset=UTF-8

Hi Dmitry,

So, can we start drafting out some things?
Simple questions would help everybody to get this moving forward.
I'll compile a simple list of questions to answer that would drive the
direction on how it would be implemented.
Please ignore the formatting on HOW they are defined. Tokens can change.
Here it is:

1- Doc comments vs. outside?

2- Keep object instance creation the same? IE: @Foo vs new Foo()

3- Is constructor the only way to inject parameters?

4- What if we have optional arguments, like: @Foo("bar", null, null, "woo")?
Suppose that you wanna fix the optional arguments by declaring names (like
this: @Foo("bar", test="woo")), doesn't it collide with PHP interests of
not supporting parametrized arguments? How would parameter skipping
proposal address this in a nicer way?

5- How would you deal with inheritance? Should a method inherit the same
annotations from parent or not?
Should we add ability to flag to inherit or not? What about overrides?
Would they be allowed? Is there a vague idea on how this concept could be
achieved?

6- Would you be possible to change annotations value at runtime?

7- Would we validate annotation arguments at all? Consider as array?
Properties of objects?

8- In case we take the approach of properties of objects... how would we
flag that a given class can/cannot be used as annotation: another
annotation, interface, any other idea?

9- Would we and/or wow would we flag that a given class could be used only
in a class and not in a method?

10- How would it be the syntax to declare a new annotation?


I think we have a good start now... =)

[]s,


On Fri, Feb 6, 2015 at 12:53 PM, Dennis Birkholz <dennis@birkholz.biz>
wrote:

> > On the other hand you have a working solution.
> > You won't be able to use annotations for PHP5 projects anyway.
> > Except, if we put them into comments or doc-comments.
> >
> > /**[Attribute(Value)]*/
>
> Why not /**@ Attribute Value */ or /**@ Attribute(Value) */? No []
> required and @ looks more familiar with docblock annotations in use.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


-- 
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--20cf3043530a8be842050e6f7fc2--