@Daniel Hunsaker Yes, the idea was a generic solution that would cover all
tags, not just @throws.
@Miguel Rosales Possibility to prevent inheritance of individual entries of
a tag seems overkill to me, and it would lead to a major change in the PSR.
Currently either all entries of a tag are
According to the current version of PSR-19, PHPDoc is implicitly inherited,
and even when PHPDoc is present in both the subclass and the superclass,
tags that are present in the superclass' PHPDoc but not in the subclass'
PHPDoc are inherited.
I think this is a very good idea, but I see a
Would it be interesting to include a @triggers tag in PSR-19? This would be
used with code that may call trigger_error() or other code that may trigger
errors, such as filesize(), mime_content_type(), filemtime(), md5_file(),
pspell_new(), etc. (There are really many!)
Examples would be:
PSR-12 states that
All binary and ternary (but not unary) operators MUST be preceded and
> followed by at least one space
Sometimes I find it useful to write arithmetic operators without
surrounding whitespace, since it can help make the meaning clear at a
glance.
Consider this very simple
