Do not remove "class foo" comments.

[carusogabriel]

Discovered in doctrine/mongodb-odm#2014 (comment)

[Ocramius]

Disagree here: "class foo" in comments is easily replaced by @see FQCN instead, which is more valuable.

[greg0ire]

@Ocramius the issue at hand is "Initializes this instance with the specified document manager, unit of work and\nclass metadata." being unduly truncated, "Initializes this instance with the specified document manager, unit of work and\n@see foo" would raise some eyebrows :P . IMO the right fix would be to remove it iff it the line before is /**, but that's probably not possible, the best thing after that probably being @carusogabriel 's solution.

[greg0ire]

The build fails, you are probably supposed to add this in the output class too.

[ostrolucky]

Issue is easily worked around by splitting the sentence differently. I think few false positives with this workaround are better than missing some some useless comments.

[malarzm]

Issue is easily worked around by splitting the sentence differently.

Come on, this is a hack for a broken rule

[ostrolucky]

I wouldn't say it's broken, just imperfect. And let's not make "hack" word even more meaningless than it is. Hitting enter at different part of sentence is hardly hacking. Regex could be improved by taking preceding content into consideration. Just making it case sensitive is lazy solution impacting false negatives too much IMHO.

[SenseException]

Depending on the context of the comment, I agree with @Ocramius to add @see. But something like a broken build because of class foo in a comment is an unexpected behavior for a user, which is why I'm for this change. "class" won't always be a reference to another class in a comment:

/**
 * Lorem ipsum dolor sit amet. That is why we like to have our
 * class final
 */

[ostrolucky]

Regex could be improved by taking preceding content into consideration