|
Yeah I hate the new comment style... it is very un-reader-friendly when reading source... and that is what we spend most of our time doing, no?
I spent 2 years writing Java and using Javadoc format... and I thought that javadoc was uncool because it was a domain-specific format...
But now I see the irony that MS has chosen an "industry standard" format (XML) and I hate it and long for the days of javadocs or doxygen again!
|
|
|
|
|
I have mixed feelings about the /// xml style. I love how it makes documentation easy, but as many others have said, it makes reading the source code tough.
I wish VS.NET had an easy way to toggle whether the comments were visible or not. (If someone has a way or a good macro that does the trick, I'd love to hear!)
<insert incredibly="" witty="" sig="" here...="">
|
|
|
|
|
I just love the /// xml comments, since I don't have to look at the source code to find out what the functions does a couple weeks down the road.
I have really bad memory
|
|
|
|
|
I think it is great having the /// comments. I generate good documentation, and the code and ddocumentation source comes from the same location. I use a similar method in my XSLT's, and a similar, but much cruder method in my javascripts
Being in a minority of one, doesn't make you insane (George Orwell , I think)
|
|
|
|
|
|
My programming assignments have to be commented heavily so I usually use the old school method, although its python not C/C++ so it is more like # blah blah blah
Matt Newman Sonork: 100:11179
"If you're Noah and you're facing the Flood, don't call a lawyer, start building an Ark." - David Cunningham
|
|
|
|