The most worthless comment ever
-
///////////////////////////////End/////////////////////////////
Found at the end of a source file :sigh:.
Software Zen:
delete this;At least it's accurate.
Did you know: That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
-
///////////////////////////////End/////////////////////////////
Found at the end of a source file :sigh:.
Software Zen:
delete this;You have just performed floccinaucinihilipilification!
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
-
///////////////////////////////End/////////////////////////////
Found at the end of a source file :sigh:.
Software Zen:
delete this;that is not worthless at all, I tend to put some END statement in all my files, be it code sources or text documents. In documents, I usually put "End Of Document" or "EOD"; in source files "// EOF" It tells you you've got all of it, nothing got lost while copying, transmitting, or whatever it is these files have to go through. I must admit I don't do it for C# files as they have a namespace with curly brackets, so you can't have a partial file and not notice, at least as long as you only put one namespace statement in a file. EOM
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
You have just performed floccinaucinihilipilification!
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
-
You have just performed floccinaucinihilipilification!
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
Will my palms grow hair because of it?
Software Zen:
delete this; -
that is not worthless at all, I tend to put some END statement in all my files, be it code sources or text documents. In documents, I usually put "End Of Document" or "EOD"; in source files "// EOF" It tells you you've got all of it, nothing got lost while copying, transmitting, or whatever it is these files have to go through. I must admit I don't do it for C# files as they have a namespace with curly brackets, so you can't have a partial file and not notice, at least as long as you only put one namespace statement in a file. EOM
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
That may have been a good idea in the punch card era, but I haven't worried about that sort of thing in almost 30 years. Besides, given the programmer involved, I know that wasn't the intent. I'm not sure what it was, but that wasn't it.
Software Zen:
delete this; -
That may have been a good idea in the punch card era, but I haven't worried about that sort of thing in almost 30 years. Besides, given the programmer involved, I know that wasn't the intent. I'm not sure what it was, but that wasn't it.
Software Zen:
delete this; -
///////////////////////////////End/////////////////////////////
Found at the end of a source file :sigh:.
Software Zen:
delete this;hmm, I've actually used "delete this" before, in C++, is that bad? ;P
-
hmm, I've actually used "delete this" before, in C++, is that bad? ;P
Not if you know what you're doing.
Software Zen:
delete this; -
That ascribes a reasoned motive for the comment.
Software Zen:
delete this; -
///////////////////////////////End/////////////////////////////
Found at the end of a source file :sigh:.
Software Zen:
delete this;how about?
// enumerating i from 0 to 10 (Lloyd 29 07 2010)
for (int i = 0; i < 10; i++)
{
// printing i to the console (Lloyd 29 07 2010)
Console.WriteLine(i);
// TODO should do something more useful later (Lloyd 29 07 2010)
}A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
how about?
// enumerating i from 0 to 10 (Lloyd 29 07 2010)
for (int i = 0; i < 10; i++)
{
// printing i to the console (Lloyd 29 07 2010)
Console.WriteLine(i);
// TODO should do something more useful later (Lloyd 29 07 2010)
}A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
At least those comments describe what the code is doing.
Software Zen:
delete this; -
At least those comments describe what the code is doing.
Software Zen:
delete this; -
how about?
// enumerating i from 0 to 10 (Lloyd 29 07 2010)
for (int i = 0; i < 10; i++)
{
// printing i to the console (Lloyd 29 07 2010)
Console.WriteLine(i);
// TODO should do something more useful later (Lloyd 29 07 2010)
}A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
Super Lloyd wrote:
// enumerating i from 0 to 10 (Lloyd 29 07 2010) for (int i = 0; i < 10; i++)
Your comments are not accurate. You are enumerating from 0 to 9!
Pete
-
I personally don't find it necessary to worry that my editor is going to somehow 'fall off the end' of a file, and mark that end with a comment. That's like wearing a seat belt in your desk chair, because you're worried that the Earth's gravity might fail.
Software Zen:
delete this; -
Super Lloyd wrote:
// enumerating i from 0 to 10 (Lloyd 29 07 2010) for (int i = 0; i < 10; i++)
Your comments are not accurate. You are enumerating from 0 to 9!
Pete
Oops! :-O
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
how about?
// enumerating i from 0 to 10 (Lloyd 29 07 2010)
for (int i = 0; i < 10; i++)
{
// printing i to the console (Lloyd 29 07 2010)
Console.WriteLine(i);
// TODO should do something more useful later (Lloyd 29 07 2010)
}A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
Super Lloyd wrote:
// TODO should do something more useful later (Lloyd 29 07 2010)
That one is actually useful - it triggers Visual Studio to add it to the Tasks List. Visual Studio Tasks List[^]
Did you know: That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
-
how about?
// enumerating i from 0 to 10 (Lloyd 29 07 2010)
for (int i = 0; i < 10; i++)
{
// printing i to the console (Lloyd 29 07 2010)
Console.WriteLine(i);
// TODO should do something more useful later (Lloyd 29 07 2010)
}A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
You have just performed floccinaucinihilipilification!
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
-
Super Lloyd wrote:
// TODO should do something more useful later (Lloyd 29 07 2010)
That one is actually useful - it triggers Visual Studio to add it to the Tasks List. Visual Studio Tasks List[^]
Did you know: That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
UNless it's changed in 2k10 I don't think the task list is particularly useful outside of VB because of non-overridable language specific behavior. In VB it shows all the TODOs in the solution. In C# it shows all the TODOs in open files. In C++ it shows all the TODOs in the file being edited. The latter two are near useless in larger projects. Instead I litter my .cs files with
#warning TODO blah...lines.3x12=36 2x12=24 1x12=12 0x12=18
