comments

问题 Is there a good reason for this? Lame question, but I just wondered if there was a reason why. 回答1: The syntax for comments in CSS is: /* comment here */ The // is not a valid syntax. I guess this allows CSS to work correctly when stripped from whitespace and new line characters during minification. 回答2: Because the specification allows for /**/ but not // :) Seriously, though, CSS treats newlines like all other whitespace, and would not be able to determine the end of the comment without a

问题 Are these nested comments allowed in a XML file? <!-- Making only one observation attempting to correct the error code --> <!-- <component> <!-- Result observation template --> <!-- <id root="2.16.840.1.113883.19.5.10" extension="103220"/> </component> --> 回答1: No, the string -- is not permitted to appear within comments in XML. So the fact you have -- show up inside another comment is going to cause failures. And trying to post that answer also broke the text entry parsing ;) For further

问题 Does anyone know what something like OR 1# means in the context of mysql injection? 回答1: It is MySQL's version of the line comment delimiter. In standard SQL, the line comment delimiter is -- . -- This is a standard SQL comment. # This is a MySQL comment. So in the context of SQL injection, if the attacker knows you're using MySQL he may use it to abruptly terminate the malicious SQL statement, causing MySQL to ignore whatever is behind the # and execute only the stuff that comes before it.

问题 Is it possible and safe to use inline comments for .ini files with PHP? I prefer a system where the comments are inline with the variables, coming after them. Are the some gotchas concerning the syntax to be used? 回答1: INI format uses semicolon as a comment character. It accepts them anywhere in the file. key1=value ; this is a comment key2=value ; this is a comment too 回答2: If you're talking about the built-in INI file parsing function, semicolon is the comment character it expects, and I

问题 I'm doing some exploratory work where I will most likely be spending 30 min on several different variations of the same task. I want to track them in git so I can jump back and forth between approaches. And if there are 3 or 6 or 9 branches, I might need some more info than the branch name to tell them apart. What is the cleanest way to attach a comment to a new branch? 回答1: You want branch descriptions: git branch --edit-description This will open up your editor and let you attach metadata

问题 So I only recently discovered the TODO comment. For those of you that don't know, most modern IDE's will recognize this word in a comment and flag the comment line a different colour so It stands out. EG. //Need to talk to Bill about refactoring this code //TODO:Need to talk to Bill about refactoring this code You may notice in IDE's like Eclipse or Rubymine highlight the TODO comment and some nice other features to do with it. My question is: What other keywords are there like the TODO? It

问题 I am using something similar to this and it will not display the Summary or Remarks when I am attempting to use the Intellisense for this function? ''' <summary> ''' Summary ''' </summary> ''' <param name="param">The Parameter.</param> ''' <remarks> Remarks </remarks> any ideas? 回答1: Need to goto Projects -> Project Properties -> Compile and turn on XML Generated File to generate the comments file.. Then build your project and it will work =) 来源： https://stackoverflow.com/questions/1329338

问题 When is it appropriate to use a block comment at the beginning of methods, and when is it appropriate to use a javadoc-style comment? From the "Comments" section of the Java style guide, I found this: Java programs can have two kinds of comments: implementation comments and documentation comments. Implementation comments are those found in C++, which are delimited by /*...*/ , and //. Documentation comments (known as "doc comments") are Java-only, and are delimited by /**...*/ . Doc comments

问题 When is it appropriate to use a block comment at the beginning of methods, and when is it appropriate to use a javadoc-style comment? From the "Comments" section of the Java style guide, I found this: Java programs can have two kinds of comments: implementation comments and documentation comments. Implementation comments are those found in C++, which are delimited by /*...*/ , and //. Documentation comments (known as "doc comments") are Java-only, and are delimited by /**...*/ . Doc comments

问题 This question already has answers here : Multiline Comment Workarounds? (10 answers) Closed 6 years ago . I found this old thread (from over a year ago), which explains how come R doesn't support a multi-line comments (like /* comment */ of PHP, for example). I am wondering if this has been resolved in the past year, or if there are other alternatives? (For example, in notepad++ with npptor, you can mark a bunch of lines and press ctrl+q to mark them all as comments, are there similar