Skip to content
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

#-comments #71

Closed
GoogleCodeExporter opened this issue Mar 21, 2015 · 6 comments
Closed

#-comments #71

GoogleCodeExporter opened this issue Mar 21, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

Hi,

could you pls replace '#' comments with the '//'

Thanks

Original issue reported on code.google.com by m...@mail.ru on 18 Sep 2013 at 7:26

@GoogleCodeExporter
Copy link
Author

Why?

Original comment by mewp...@gmail.com on 18 Sep 2013 at 8:12

@GoogleCodeExporter
Copy link
Author

well, there is nothing wrong with linux shell comments in php,as official 
documentation states...

It is just a feature request... I am trying to conform this 
http://kohanaframework.org/3.3/guide/kohana/conventions#comments maybe it also 
makes sense for you... 

also these sharp comments got my syntax highlighter  just crazy :)

Original comment by m...@mail.ru on 18 Sep 2013 at 10:01

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

if you have not a time for that then I could prepare a patch

Original comment by m...@mail.ru on 18 Sep 2013 at 10:15

@GoogleCodeExporter
Copy link
Author

sh (and other shells), python, perl, ruby, php, tcl, and other languages use 
#-comments. If your syntax highlighter can't handle that, it's a bug with the 
highlighter, not with LightOpenID code.

php, c/c++, and java use //-comments. I personally think that #-commments are 
more fitting for a dynamic language, but regardless -- I don't see a reason to 
include a patch changing a completely arbitrary thing in the code, that doesn't 
affect functionality, readability, robustness, or really anything else.

Furthermore, I don't consider kohana framework style conventions a superior 
(or, for that matter, inferior) to other conventions, including the one that 
LightOpenID uses.

In one sentence: It would be a useless change.

Original comment by mewp...@gmail.com on 19 Sep 2013 at 11:01

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant