Style Cop
-
Rob Philpott wrote:
But that's not a justification for using camel case
Rob Philpott wrote:
It absolutely is.
No, it's a justification for using a standard. It's not a justifcation for selecting camel case as that standard. Your point about "You can tell at a glance what you're dealing with (local/member/property etc). And if we all do things the same way it makes it easier to understand each other's code." are entirely valid, and I agree with them, but they apply just as much to Hungarian notation as camel case.
Electron Shepherd wrote:
But that's not a justification for using camel case
Electron Shepherd wrote:
It absolutely is.
Electron Shepherd wrote:
No, it's a justification for using a standard.
Uh-huh. Ok it's not a justification for using camel case for its own merit, its justification for using camel case because that is the standard. Better?
Regards, Rob Philpott.
-
I know you have a nice sense of humor, that’s why I allow myself a crude jokes sometimes. :)
There is only one Ashley Judd and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
Go ahead, we are all crude people here, so the cruder the humor, the funnier it is for all of us :)
Regards, Nish
My technology blog: voidnish.wordpress.com
-
Electron Shepherd wrote:
But that's not a justification for using camel case
Electron Shepherd wrote:
It absolutely is.
Electron Shepherd wrote:
No, it's a justification for using a standard.
Uh-huh. Ok it's not a justification for using camel case for its own merit, its justification for using camel case because that is the standard. Better?
Regards, Rob Philpott.
Not really. It still doesn't explain why it's the standard in the first place. That's what I'm trying to userstand. Lots of people use camel case as a naming standard, but no-one seems able to say why it's better than the others. So, if you were tasked with developing a set of coding standards, and you decided to use camel case for variables, would you be explain to someone the benefits of that over an MFC-style
str...or C-stylelpsz...convention? -
Not really. It still doesn't explain why it's the standard in the first place. That's what I'm trying to userstand. Lots of people use camel case as a naming standard, but no-one seems able to say why it's better than the others. So, if you were tasked with developing a set of coding standards, and you decided to use camel case for variables, would you be explain to someone the benefits of that over an MFC-style
str...or C-stylelpsz...convention?Dude, I've told you I don't know why it's the standard, probably because they nicked it from Java at a guess. Standards aren't always designed, sometimes they just get adopted and evolve despite being imperfect. Who knows? I would expect Hungarian got dropped due to the better Intellisense handling in Visual Studio at its mainstay 'p_' no longer holding any worth. In short its benefits got outweighed by its clumsiness.
Regards, Rob Philpott.
-
Dude, I've told you I don't know why it's the standard, probably because they nicked it from Java at a guess. Standards aren't always designed, sometimes they just get adopted and evolve despite being imperfect. Who knows? I would expect Hungarian got dropped due to the better Intellisense handling in Visual Studio at its mainstay 'p_' no longer holding any worth. In short its benefits got outweighed by its clumsiness.
Regards, Rob Philpott.
Rob Philpott wrote:
I don't know why it's the standard
I'm not asking why it's the standard where you are. You seem to like it as a naming convention. What I'm asking is why you like it. Why do you think it's better than the others? I may have misinterpreted your opinion of course. You may dislike it as much as I do...
-
Rob Philpott wrote:
I don't know why it's the standard
I'm not asking why it's the standard where you are. You seem to like it as a naming convention. What I'm asking is why you like it. Why do you think it's better than the others? I may have misinterpreted your opinion of course. You may dislike it as much as I do...
Actually, it's not something I feel deeply passionate about. Kind of indifferent to it as a choice, kind of like it because it is a standard and I can, for instance, tell what's a type (Pascal) and what's a variable (Camel) at a glance. Thank God, it's time to go to the pub now (almost)...
Regards, Rob Philpott.
-
I started to check out StyleCop this morning. I'm not going to rant about every other rule it follows, but has anyone noticed that the file **.Designer.cs violates:
SA1201: All methods must be placed after all fields.
Windows creates this file. I think I'm done with StyleCop.
I don't like style cop unless I am offshoring unthinking work to unthinking developers. True software is written by creative professionals. If I wanted to be micromanaged I would work in a call center.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
No, FxCop and StyleCop are different. StyleCop analyzes your source code, whereas FxCop does static analysis on your compiled assembly. Normally you are supposed to use them together, so they complement each other.
Regards, Nish
My technology blog: voidnish.wordpress.com
They complement each other, but they certainly don't compliment you. BTW - they work really well in combination with NDepend.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
-
They complement each other, but they certainly don't compliment you. BTW - they work really well in combination with NDepend.
I'm not a stalker, I just know things. Oh by the way, you're out of milk.
Forgive your enemies - it messes with their heads
Pete O'Hanlon wrote:
BTW - they work really well in combination with NDepend.
Interesting. Never used NDepend myself though.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
I started to check out StyleCop this morning. I'm not going to rant about every other rule it follows, but has anyone noticed that the file **.Designer.cs violates:
SA1201: All methods must be placed after all fields.
Windows creates this file. I think I'm done with StyleCop.
So? Edit it. Big fat hairy deal. I delete mine and put that crap in the main file like VS 2002 and 2003 do. Just because I can. :-D
-
me too. which is why i think LINQ is crap.
I find LINQ quite readable in most cases.