Added some tests for #6499

[rahuldroy]

No description provided.

[Ocramius]

Note that CS tests fail because of this intentional trailing space. Not sure yet about how to fix it.

[samsonasik]

@Ocramius it seems we can set exclude for this file at .php_cs file ?

[Ocramius]

@samsonasik that's some real good news, thanks! :-)

[Ocramius]

Linking #6499

[weierophinney]

@Ocramius is this an issue specific to our annotation support, or is it an issue in the Doctrine annotation library?

[Ocramius]

Still not clear. I personally think Zend\Code may be passing a different string to the annotation parser.

[weierophinney]

Removed milestone, as we cannot reliably reproduce.

In discussion with @Ocramius, it's possible that Zend\Code is passing an invalid string to the annotation parser. In looking at Zend\Code\Reflection\ClassReflection, however, the method we call is getAnnotations(), which passes the results of getDocComment() -- which is inherited directly from ReflectionClass. As such... this is very difficult to track.

[nickurt]

@weierophinney @Ocramius Thanks for the reply's, I debugged some things.

The file Zend\Code\Scanner\AnnotationScanner -> __construct returns the correct docComment, but it fails in the tokenize function (#ref).

The currentChar (#ref) is here ...

string(1) "/"
string(1) "
"
string(1) " "
string(1) "
"
string(1) " "
string(1) "
"
string(1) " "
string(1) "
"
string(1) " "
string(1) "
"
string(1) " "
string(1) "
"
string(1) " "

[Ocramius]

I see that this has indeed nothing to do with doctrine/annotations. Removing myself from the assignees as I cannot help with this issue right now.

[Maks3w]

Do #7113 fix this?

[GeeH]

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html
New issue can be found at: zendframework/zend-code#79