4 ms·
Yeah, that's the standard way to write comments. It looks terrible but it's not bad to write because Visual Studio auto-generates the comment skeleton for you.
by almenon 9y ago
Yeah, that's the standard way to write comments. It looks terrible but it's not bad to write because Visual Studio auto-generates the comment skeleton for you.
- jackewiehose 9y agoEmbedding XML inside a C-comment (as a standard) is just fucked up. Do you have correct syntax highlighting with that? (I don't. But even if emacs would understand this, it's still wrong)
- MichaelGG 9y agoYeah, it's a mess. F# got it right, use triple slash to provide a summary. C# should have at least gotten that, instead of forcing so much XML all the time.
- _dcwr 9y agoC++ with Doxygen and Java with Javadoc are much saner formats for this purpose. What's even worse is that Visual Studio 2015 just vomits out that the XML is malformed when I have C++ headers with Doxygen style comments in them. It detects the three slashes and tries to apply C# XML docs parsing to them and that of course fails. Meanwhile NetBeans can handle them no problem and display parsed docs in pop ups.
- colejohnson66 9y agoIt’s not the standard way. It’s the standard way for documentation so Intellisense can provide information about the function. The standard way still uses C/C++ style double slash ( // ) and multiline style ( // )
- techtalsky 9y agoMuliline style /
- colejohnson66 9y agoI meant the slash-asterisk comment asterisk-slash, but apparetly HN saw the two asterisks as markup...