Electronics & Programming


Open Source electronics development and programming

  • You are not logged in.
  • Root
  • » PHP
  • » Traits and Conflicts: Collisions as Warnings or Fatal? [RSS Feed]

#1 Dec. 5, 2010 14:04:57

Stefan M.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

Traits and Conflicts: Collisions as Warnings or Fatal?


While preparing some explanations on how to use traits, I stumbled over an
inconsistency in the current implementation.

Currently collisions, if they are explicit in the code, lead to a warning and
are resolved by explicit exclusion of the two methods that collide.
However, there are other ways to provoke a collision, for instance by
introducing a new alias during composition.

http://svn.php.net/viewvc/php/php-src/trunk/Zend/tests/traits/error_015.phpt?revision=305512&view=markuphttp://svn.php.net/viewvc/php/php-src/trunk/Zend/tests/traits/language010.phpt?revision=305512&view=markupCollisions usually point to implementations that changed unexpectedly, and the
implicit resolution might be problematic since it could hide the real cause for
a bug.

So, should that warning be changed to a fatal error, or should the other fatals
be warnings, too?

Best regards

Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgiumhttp://soft.vub.ac.be/~smarrPhone: +32 2 629 2974
Fax: +32 2 629 3525

PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:http://www.php.net/unsub.php


  • Root
  • » PHP
  • » Traits and Conflicts: Collisions as Warnings or Fatal? [RSS Feed]

Board footer

Moderator control

Enjoy the 24th of May

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support