I agree with you that having both only lead to confusion. However we could certainly argue a long time about which one should be kept.
When starting a project from scratch it's probably easier to mark a few method as public, rather than most code as private. It seems more "secure" to whitelist public thing, rather than blacklist private thing. On the other hand, like you said, for an existing project, it's likely easier to gradually make things private. Maybe that's the reason both annotations exist ? to allow to choose between "whitelist" or "blacklist" workflow ? But whatever reason may have lead to the current situation, I would be in favor to keep only one, whichever it is. It might even be possible to write a tool to migrate from one annotation to another, once the choice is settled. -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/fa76e6eb-627b-4dc6-becc-477428caae1b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
