|
honey the codewitch wrote: an icepick around for rebooting their users
Software Zen: delete this;
|
|
|
|
|
honey the codewitch wrote: icepick around for rebooting their users
Is that what they call a LART in your part of the world? 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
something like that, yes.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: my hubby used to work helldesk in college and he said he kept a paperclip around for rebooting the imacs and an icepick around for rebooting their users.
Too bad I can't use that technique.
|
|
|
|
|
Gary Wheeler wrote: _Users_Terminate();
just don't let Sander catch you writing leading underscores in your method names.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: writing leading underscores in your method names
I'm doing it consistently(*), as is the rest of my group, so it is therefore unassailably correct.
(*) Our convention is that non-public values are named with a leading underscore.
Software Zen: delete this;
|
|
|
|
|
You have my blessings on the underscore
But why is there a comment that just puts the two words of the function name in a different order? 
Why not change the function name to _Terminate_Users (or TerminateUsers if you want to do it right  ) so it's slightly more readable and ditch the comment?
|
|
|
|
|
Sander Rossel wrote: Why not change the function name to _Terminate_Users (or TerminateUsers if you want to do it right )
That was last month. The coding standard of this month says that functions should be named _<class>_<action>. The argument for that is that in a sorted list of function names, you get all the actions on one object class gathered together.
I have no information wha will be the right way to format code next month, or what the arguments will be, but I am really happy that modern IDEs have support for coding style changes. For newlines, indents and spacing it can be fully automated. Changing naming standards usually require some more manual work, but compared to the old days where you had to manually search for every occurence of a symbol to change it to the standard of the month required a lot more work.
|
|
|
|
|
Fortunately for me, our coding standard (all 1½ pages of it) hasn't changed significantly since 2000.
Software Zen: delete this;
|
|
|
|
|
The comment was removed shortly thereafter. The "user termination" logic was directly after the comment, but was moved into its own method. This was part of a reorganization/refactoring going on in preparation for a new feature.
Software Zen: delete this;
|
|
|
|
|
The best comment is a removed comment 
|
|
|
|
|
A long time ago I took a programming class from Dan Saks, one-time secretary of the ISO C++ standardization committee. He said something to us which has stuck with me ever since, and has led to a profound reduction in the number of comments I write:
"If you can, say it in code. If you can't, only then say it in a comment."
While we do maintain change history in our source, my comments now tend to serve other purposes than simple documentation. For example, our code base is in the neighborhood of 3 million lines so navigation can be a problem. Comments can serve as markers for 'find in files' destinations when Intellisense doesn't work.
Software Zen: delete this;
|
|
|
|
|
One of my mentors once stated
"The comments are the part of the code that even the compiler cannot understand"
|
|
|
|
|
I do similar. Private members have leading underscores in my code.
I was just yanking Sander's chain.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: yanking Sander's chain
Chain-yanking is almost always a useful thing.
Software Zen: delete this;
|
|
|
|
|
I find the comment more problematic.
But it's good that I instill fear in those that write code of dubious quality*
* The quality of code shall be measured by braceless single line if statements, indentation, lack or abundance of white space, naming conventions and comments.
Whether the code does what it should do is of secondary concern.
Code written in Java shall be considered bad quality by default.
|
|
|
|
|
see, I used to care about that stuff.
now it's (re other people's code)
a) does the code do what it's supposed to?
b) can i read it?
i guess i've gotten good at b because i'm fine with just about whatever.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Technically is just a line of code.
-- Carlo The Nitpick
|
|
|
|
|
Software Zen: delete this;
|
|
|
|
|
There's no such thing as a "line of code" in C-style languages.
|
|
|
|
|
You mean I've spent all these years doing... nothing? 
Software Zen: delete this;
|
|
|
|
|
The function name is clear enough, is the comment necessary?
|
|
|
|
|
And I thought the problem was:
_Users_Terminate( IgnoreUser=Me ); // Bug found that after terminating my user, program stopped...
|
|
|
|
|
10 PRINT "WEEEEEE",
20 GOTO 10
|
|
|
|
|
A tad BASIC, but sounds like fun.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
