-
Notifications
You must be signed in to change notification settings - Fork 443
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
remove redundant space from xerbla call sbgv/hbgv #792
remove redundant space from xerbla call sbgv/hbgv #792
Conversation
Codecov ReportBase: 0.00% // Head: 0.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #792 +/- ##
=======================================
Coverage 0.00% 0.00%
=======================================
Files 1908 1908
Lines 187072 187072
=======================================
Misses 187072 187072
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Thanks. I do not have a strong opinion about these white spaces. Either way is fine. Thanks for the PR. That's great. |
I just wrote a small unit test to see the error message, which xerbla returns, and it is failed due to additional space in function name. Now behaviour is aligned with other LAPACK functions. Thanks for the merge! |
Ah! OK. Thanks for letting me know. Perfect then. |
Actually many (most?) five-letter functions that use XERBLA have this trailing space, maybe it is the unit test that needs to be more flexible ? |
OMG, indeed. I am sorry, I did not check other 5 letter functions... Is it done for special purpose? LAPACK namings can be more than 6 letters. Yeap, unit test can be changed, but it should be? Unfortunately, trailing space led to misundersanding from my side. It could be reverted if there exists LAPACK standard in such case. But for my point of view it is not aligned between functions. |
No, this is a remnant of FORTRAN 77. Six-letter is not needed any longer. The space in the parameter passed to XERBLA is not needed any longer. The code with a space XERBLA should work with a space in the name of the subroutine. So it does bother me that the code with a space is a problem on your end. That being said, we can remove the space. I do not mind. LAPACK namings can be more than 6 letters. I agree with @martin-frbg that we want to be consistent across 5-letter-name subroutines. |
@langou thank you for comprehensive explanation! Of course, it would be nice to have the same style for all 5-letter-name subroutines. Indeed, not all are aligned. For example, |
Part of issue #791.