Re: [PHP-DEV] Traits and Properties

2010-12-13 Thread Larry Garfield
On Monday, December 13, 2010 10:02:13 am Stefan Marr wrote: > However, since traits do not provide any safety provisioning for state, > i.e., there is no collision handling for properties, the question is, how > do we either promote to use explicit accessors or how do we deal with the > inevitable

RE: [PHP-DEV] Traits expecting interfaces implicitly leads to expensive runtime checks

2010-12-13 Thread Jonathan Bond-Caron
On Sun Dec 12 04:33 PM, Nathan Nobbe wrote: > > > So the 'with/within' tokens would apply to traits. > > I feel 'expect', 'need', 'require' etc sound better, matter of opinion > really, but it sounds like from an internals perspective it's > preferred to reuse existing keywords if possible. >

Re: [PHP-DEV] Re: ts_free_thread() frees only temporary in multiple parallel threads

2010-12-13 Thread Benjamin Franke
I referred to the following version of php_embed2: http double dot slash slash svn.tobin.nl/public/php/embed2/trunk/ This seems to be an official php release especially for multi-threaded usage but it is not included in official sources. I just compiled it with my sources and followed the example

Re: [PHP-DEV] Traits and Properties

2010-12-13 Thread Stefan Marr
Hi Richard: On 13 Dec 2010, at 14:31, Richard Quadling wrote: > On 11 December 2010 23:31, Stefan Marr wrote: >> The current status of the property behavior is not yet documented explicitly > > On the assumption that traits WILL include properties (with > visibility) and aliasing can do all its

Re: [PHP-DEV] Traits and Properties

2010-12-13 Thread Stefan Marr
Hi Richard: On 13 Dec 2010, at 14:13, Richard Quadling wrote: > From the rfc [1], "A Trait is similar to a class, but only intended to > group functionality". > > I'm guessing that says it all. A trait has no properties. It is really a practical concern of language consistency for the moment. I

Re: [PHP-DEV] Traits and Properties

2010-12-13 Thread Richard Quadling
On 11 December 2010 23:31, Stefan Marr wrote: > The current status of the property behavior is not yet documented explicitly On the assumption that traits WILL include properties (with visibility) and aliasing can do all its magic, how would the situation be handled where multiple traits define s

Re: [PHP-DEV] Traits and Properties

2010-12-13 Thread Richard Quadling
On 11 December 2010 16:47, Stefan Marr wrote: > Hi: > > Traits do not provide any special provisioning for handling properties, > especially, there is no language solution for handling colliding property > names. > The current solution/idiom for handling state safely in a trait is to use > eith