-
-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Files that have only \r (CR, 0x0d) EOL characters are not handled correctly #885
Comments
Example file: source_without_lf_only_cr.php.txt |
Do you still see this problem in php-code-coverage 9.2.11? |
Yes, unfortunately.
|
It appears that you have different installations of PHPUnit mixed up. For instance, you may have used Composer to install PHPUnit and have configured the autoloader generated by Composer as PHPUnit's bootstrap script but then you invoke PHPUnit using an executable other than
|
Files that have only \r (CR, 0x0d) characters on line ends and having at least two comment lines cause failure:
Linux command
wc -l
shows 0 for these files beacuse it counts LF characters. Number of lines is 1 because no LF characters are in the file.$nonCommentLinesOfCode = 1-2 = -1
triggers the bug.Macintosh files before OS X had this type of line endings.
Similar to previously fixed issue #831.
The text was updated successfully, but these errors were encountered: