|
This guy had his head full of coffee (or other drugs, can't say exactly)
Maybe the code where longer before and was shortened to this 
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
Would a simple error be a ground-breaking concept for you?
|
|
|
|
|
Vitaly Tomilov wrote: Would a simple error be a ground-breaking concept for you?
What is that suppose to mean? 
|
|
|
|
|
Looks like a simple error, which needs a simple fix.
|
|
|
|
|
Vitaly Tomilov wrote: Looks like a simple error, which needs a simple fix.
Firstly, simple error yes, but why is this not spotted a mile away?
Secondly, this is not my code. It is Microsoft's production code, that lives in VS2010 and VS2012. It is up to them to fix such a simple error.
|
|
|
|
|
I found 100+ StringBuilders in a module(see below).
function string function1()
{
System.Text.StringBuilder sb1 = new System.Text.StringBuilder();
....
...
}
function void method1()
{
System.Text.StringBuilder sb2 = new System.Text.StringBuilder();
....
...
}
function string function3()
{
System.Text.StringBuilder sb3 = new System.Text.StringBuilder();
....
...
}
....
...
 Then I have Included the namespace at top of the module.
using System.Text;
And replaced System.Text.StringBuilder with StringBuilder
thatrajaNobody remains a virgin, Life screws everyone 
|
|
|
|
|
This isn't like a hidden bug or the things we usually see over here...
I think CP has some people that maybe like that style...
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
Just a little reminder: This is the "Hall Of Shame" and not he "Hall Of Bugs". There is no good reason to clutter ones code with superflous repetitions of the namespace prefixing the StringBuilder, except maybe when there is another implementation of StringBuilder floating around.
Just my two cents! 
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
|
|
|
|
|
I don't see the shame on this, this guy just like to write long names 
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
|
I was talking about the original programmer, is that you?
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
Sentenryu wrote: I was talking about the original programmer, is that you?
No
thatrajaNobody remains a virgin, Life screws everyone
|
|
|
|
|
That's not "style", but a "preference"; the difference is that one needs arguments, the other doesn't. People who prefer the long naming should try prefixing everything with "global::".
Bastard Programmer from Hell 
|
|
|
|
|
Personally, I always import, unless there is already something with the same name imported.
But it's a matter of taste.
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
Sentenryu wrote: I always import
But that's not what the using directive does. There is no "import" in C# -- the closest to that is references.
|
|
|
|
|
my teachers always said import here in Brazil, I ended up picking up the habit...
I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)
|
|
|
|
|
Sentenryu wrote: But it's a matter of taste.
No, it's not.
Bloating code is an offence. Three offences, you're out.
Bastard Programmer from Hell
|
|
|
|
|
But, some folk like to bloat their code. 
I agree, there is no good reason to do this, but it is not as bad as wacky, buggy code.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
|
CIDev wrote: I agree, there is no good reason to do this, but it is not as bad as wacky, buggy code.
To quote one of the arguments why it is;
CIDev wrote: Just because the code works, it doesn't mean that it is good code.
And that's easy to explain; the more symbols you need to convey an idea, the more chances that there's an error in the communication. The more symbols, the more fluff, the more bugs.
Bastard Programmer from Hell
|
|
|
|
|
Eddy Vluggen wrote: prefixing everything with "global::".
I tried that, briefly.
|
|
|
|
|
PIEBALDconsult wrote: I tried that, briefly.
..a good idea, if you are paid per line written.
It should feel comparably to explicitly stating that a member is "private", and prefixing everything possible with "this".
Bastard Programmer from Hell 
|
|
|
|
|
Eddy Vluggen wrote: explicitly stating that a member is "private",
Which everyone should do. There should be no default access modifiers.
Eddy Vluggen wrote: prefixing everything possible with "this".
Which I also do. Just because. 
|
|
|
|
|
PIEBALDconsult wrote: Which everyone should do. There should be no default access modifiers.
Why?
PIEBALDconsult wrote: Which I also do. Just because.
The amount of symbols that you use to convey an idea would best be kept to a minimum.
Bastard Programmer from Hell
|
|
|
|
|
No, you prefix the member if a class with this to prevent any ambiguity. The method or property on it's own only implies where it is. If I have this code:
class Thingy {
private int majig = 27;
void summit() {
if (majig > 42) {
}
}
}
And I copy the test to another method, all bad things could happen:
void nuThang() {
int majig = 69;
if (majig > 42) {
}
}
oops.
Panic, Chaos, Destruction. My work here is done.
Drink. Get drunk. Fall over - P O'H
OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre
I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer
Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
|
|
|
|
|
Copy/paste is often an invitation not to check what you just pasted. Your example might be a nice example on why we introduced the DRY principle, but being this abstract, one can't be sure.
But no, I'd not be bloating my code for the sake of "easy copies". If it's that re-usable, I'll take the time to make it a snippet.
--edit;
Nagy Vilmos wrote: No, you prefix the member if a class with this to prevent any ambiguity
..the same kind of ambiguity that you have if you don't use the full name against a type, including it's namespace. Do you have global variables that clash with the names of the property/method that you're calling from the current object that you need to specify explicitly that you need the property/method from "this" object?
Bastard Programmer from Hell
modified 15-Jun-12 11:22am.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
